-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create benchmarks #255
Merged
Merged
Create benchmarks #255
Conversation
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
commet-bot
reviewed
May 31, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.50
.
Benchmark suite | Current: aa0c3e1 | Previous: f8f37c1 | Ratio |
---|---|---|---|
TimelineViewer Scrolling - Average Raster Time |
1.237185185185185 ms |
0.4608731343283582 ms |
2.68 |
TimelineViewer Scrolling - Standard Deviation of Frame Rasterizer Time |
0.7805651577503429 ms |
0.2006313210069058 ms |
3.89 |
TimelineViewer Scrolling - Worst Raster Time |
4.941 ms |
2.081 ms |
2.37 |
TimelineViewer Scrolling - 95th Percentile Raster Time |
2.54 ms |
1.291 ms |
1.97 |
TimelineViewer Scrolling - 50th Percentile Build Time |
1.896 ms |
1.109 ms |
1.71 |
TimelineViewer Scrolling - 50th Percentile Raster Time |
1.139 ms |
0.363 ms |
3.14 |
This comment was automatically generated by workflow using github-action-benchmark.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We need a reliable way to measure performance of the UI
Benchmark data will be available here and will be updated on each push. This should help us to optimise performance and detect regressions :D
At the moment i'm only benchmarking performance of the chat timeline as I felt this is the are which is most important, and seems to be slower than other parts of the app