-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ci: Capture overhead in node app #17420
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
000d08e
to
3d9bba7
Compare
85bf57a
to
c1dfc7b
Compare
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
f80f0c6
to
0ba37a7
Compare
62f223d
to
e2e4e72
Compare
dev-packages/node-overhead-gh-action/lib/markdown-table-formatter.mjs
Outdated
Show resolved
Hide resolved
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, thans for adding this!
(as discussed, some more involved endpoints would also be interesting to test against but we (anyone in the team) can add these as a follow-up)
189af8e
to
1c64a2a
Compare
This adds a simple node express app that is run on CI to get very ~~ overhead measurements of using Sentry.
THIS IS NOT NECESSARILY REPRESENTATIVE OF USING SENTRY IN A REAL APP! The app is very synthetic and real world numbers may vary wildly.
We run 3 endpoints with 3 scenarios each:
Each of these is run for 10s (after warmup) via autocannon, and we capture the average # of requests per seconds. The scenarios are:
3, With errors-only Sentry instrumentation: