-
Notifications
You must be signed in to change notification settings - Fork 722
performance headlines / landing page #2246
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
Conversation
Benchmark resultsInstruction countsSignificant differencesThere are no significant instruction count differences Other differencesClick to expand
Wall-timeSignificant differencesThere are no significant wall-time differences Other differencesClick to expand
Additional informationCheckout details:
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2246 +/- ##
=======================================
Coverage 94.65% 94.65%
=======================================
Files 102 102
Lines 23917 23917
=======================================
Hits 22638 22638
Misses 1279 1279 ☔ View full report in Codecov by Sentry. |
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.
Looks fun!
I think the numerical differences (-47%) are a bit confusing? I think a factor ("1.9x slower") would be easier to grok.
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.
Nice 👍 Glad to see some of the functionality of the site generator being helpful sooner than later.
81683f6
to
cfedab1
Compare
I think just for autoreload it has been worth it so far |
cfedab1
to
627cf45
Compare
Could you update the screenshot? I wonder if we could get this to do deploys for PRs... |
done
apparently there is a thing called "GitHub Pages preview" but "This feature is only in alpha currently and is not available to the public!" so maybe this will become easy soon? alternatively we could deploy prs to a throw-away netlify account or similar |
This PR adds a little visual display of performance "headlines" to https://rustls.dev/perf/ which looks like:
These are just server TLS1.3 handshake performance, plus TLS1.3 AES-256-GCM transfer rates, which are think is a reasonable
Most of this PR is made up of an extremely "clever" macro, which expands to an SVG I drew in inkscape and sets the dial transforms based on its inputs. I suggest this SVG is treated as write-only :)