You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
efps — editor "frames per second". The number of updates assumed to be possible within a second.
Derived from input latency. efps = 1000 / input_latency
Detailed information
🏠 Reference result
The performance result of sanity@latest
Benchmark
latency
p75
p90
p99
blocking time
test duration
article (title)
41ms
65ms
79ms
525ms
920ms
11.1s
article (body)
13ms
16ms
22ms
182ms
198ms
5.1s
article (string inside object)
37ms
39ms
42ms
52ms
150ms
6.8s
article (string inside array)
45ms
48ms
51ms
111ms
264ms
7.4s
recipe (name)
21ms
23ms
24ms
37ms
5ms
7.6s
recipe (description)
19ms
20ms
22ms
28ms
0ms
4.6s
recipe (instructions)
6ms
8ms
10ms
29ms
0ms
3.2s
synthetic (title)
50ms
53ms
63ms
197ms
655ms
12.6s
synthetic (string inside object)
50ms
54ms
60ms
449ms
1022ms
8.4s
🧪 Experiment result
The performance result of this branch
Benchmark
latency
p75
p90
p99
blocking time
test duration
article (title)
37ms
39ms
43ms
313ms
28ms
10.1s
article (body)
14ms
17ms
31ms
91ms
184ms
5.2s
article (string inside object)
35ms
38ms
44ms
176ms
138ms
6.4s
article (string inside array)
41ms
43ms
47ms
66ms
238ms
7.1s
recipe (name)
21ms
22ms
25ms
49ms
0ms
8.0s
recipe (description)
19ms
20ms
22ms
40ms
0ms
4.6s
recipe (instructions)
6ms
8ms
9ms
17ms
0ms
3.2s
synthetic (title)
51ms
52ms
60ms
128ms
357ms
14.7s
synthetic (string inside object)
48ms
50ms
54ms
604ms
1093ms
8.6s
📚 Glossary
column definitions
benchmark — the name of the test, e.g. "article", followed by the label of the field being measured, e.g. "(title)".
latency — the time between when a key was pressed and when it was rendered. derived from a set of samples. the median (p50) is shown to show the most common latency.
p75 — the 75th percentile of the input latency in the test run. 75% of the sampled inputs in this benchmark were processed faster than this value. this provides insight into the upper range of typical performance.
p90 — the 90th percentile of the input latency in the test run. 90% of the sampled inputs were faster than this. this metric helps identify slower interactions that occurred less frequently during the benchmark.
p99 — the 99th percentile of the input latency in the test run. only 1% of sampled inputs were slower than this. this represents the worst-case scenarios encountered during the benchmark, useful for identifying potential performance outliers.
blocking time — the total time during which the main thread was blocked, preventing user input and UI updates. this metric helps identify performance bottlenecks that may cause the interface to feel unresponsive.
test duration — how long the test run took to complete.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
useReleasePermissions
which checks if a user can schedule or publish a release. We will be adding more to this in a separate PRWhat to review
Does this make sense? Should we do this a different way?
Testing
Have updated the tests
To manually test you should use a user that doesn't have permissions (viewer), the debug roles don't work consistently.
Notes for release
Update permissions in the release details