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
45ms
77ms
210ms
294ms
10.8s
article (body)
15ms
18ms
22ms
145ms
54ms
5.3s
article (string inside object)
41ms
44ms
51ms
230ms
395ms
7.6s
article (string inside array)
43ms
47ms
51ms
181ms
136ms
7.1s
recipe (name)
22ms
24ms
26ms
47ms
0ms
7.5s
recipe (description)
20ms
22ms
25ms
38ms
0ms
4.8s
recipe (instructions)
6ms
8ms
10ms
23ms
0ms
3.3s
synthetic (title)
53ms
55ms
64ms
292ms
493ms
14.1s
synthetic (string inside object)
53ms
55ms
72ms
396ms
836ms
8.4s
🧪 Experiment result
The performance result of this branch
Benchmark
latency
p75
p90
p99
blocking time
test duration
article (title)
60ms
62ms
76ms
267ms
1218ms
13.2s
article (body)
15ms
17ms
37ms
209ms
329ms
5.9s
article (string inside object)
57ms
60ms
76ms
273ms
1119ms
8.9s
article (string inside array)
60ms
64ms
74ms
412ms
1395ms
9.3s
recipe (name)
38ms
42ms
49ms
93ms
96ms
9.3s
recipe (description)
34ms
35ms
39ms
81ms
34ms
6.1s
recipe (instructions)
6ms
8ms
9ms
20ms
10ms
3.4s
synthetic (title)
139ms
149ms
174ms
615ms
7355ms
23.8s
synthetic (string inside object)
139ms
145ms
157ms
449ms
5618ms
14.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.
I'm merging this one, I think it doesn't need a peer review it's just a rename of types that came from content lake, and it's going to a feature branch.
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
Content lake has renamed the events types that are returned from the events api to camel case.
This reflects that update in the studio.
What to review
Testing
Notes for release