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
Based on the stats here, I picked the jobs that use the most resources on two new images, ubuntu-latest-m and ubuntu-22.04-m, which have their own separate 60 concurrent builds limits, and have more memory and more CPU cores (as well as faster ones).
What to review
Everything should work like before, only faster and less bottlenecks on the PR checks.
Testing
If the status checks behave exactly like before (but faster) then we're good to go 👍
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)
44ms
50ms
82ms
460ms
944ms
11.6s
article (body)
17ms
21ms
34ms
198ms
573ms
6.0s
article (string inside object)
41ms
43ms
49ms
149ms
157ms
6.8s
article (string inside array)
49ms
52ms
59ms
255ms
494ms
8.0s
recipe (name)
19ms
20ms
22ms
43ms
0ms
8.2s
recipe (description)
18ms
19ms
21ms
45ms
0ms
4.5s
recipe (instructions)
5ms
7ms
9ms
18ms
0ms
3.1s
synthetic (title)
55ms
57ms
60ms
320ms
937ms
13.5s
synthetic (string inside object)
55ms
60ms
69ms
498ms
1607ms
9.1s
🧪 Experiment result
The performance result of this branch
Benchmark
latency
p75
p90
p99
blocking time
test duration
article (title)
43ms
69ms
87ms
392ms
929ms
12.6s
article (body)
16ms
18ms
24ms
80ms
62ms
5.2s
article (string inside object)
42ms
44ms
47ms
151ms
170ms
7.3s
article (string inside array)
48ms
51ms
56ms
170ms
303ms
7.3s
recipe (name)
20ms
22ms
23ms
40ms
0ms
7.6s
recipe (description)
18ms
19ms
21ms
36ms
0ms
4.5s
recipe (instructions)
5ms
6ms
7ms
19ms
0ms
3.0s
synthetic (title)
56ms
58ms
61ms
282ms
1022ms
13.2s
synthetic (string inside object)
53ms
55ms
61ms
548ms
1301ms
8.5s
📚 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
We often get congestion and bottlenecks if there's a lot of PRs being worked on, as the default
ubuntu-latest
runner has a 60 concurrent builds limit. Current queue status is visible here: https://github.com/organizations/sanity-io/settings/actions/hosted-runnersBased on the stats here, I picked the jobs that use the most resources on two new images,
ubuntu-latest-m
andubuntu-22.04-m
, which have their own separate 60 concurrent builds limits, and have more memory and more CPU cores (as well as faster ones).What to review
Everything should work like before, only faster and less bottlenecks on the PR checks.
Testing
If the status checks behave exactly like before (but faster) then we're good to go 👍
Notes for release
N/A