Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

chargome
Copy link
Member

next@canary now resolves to next 16 which is why we need to update the testing strategy here

@chargome chargome self-assigned this Oct 15, 2025
@chargome chargome requested a review from Lms24 October 15, 2025 11:02
Copy link
Contributor

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.

Scenario Requests/s % of Baseline Prev. Requests/s Change %
GET Baseline 9,205 - 9,065 +2%
GET With Sentry 1,379 15% 1,339 +3%
GET With Sentry (error only) 6,150 67% 6,068 +1%
POST Baseline 1,202 - 1,170 +3%
POST With Sentry 521 43% 481 +8%
POST With Sentry (error only) 1,056 88% 1,029 +3%
MYSQL Baseline 3,312 - 3,244 +2%
MYSQL With Sentry 498 15% 471 +6%
MYSQL With Sentry (error only) 2,745 83% 2,657 +3%

View base workflow run

@chargome chargome merged commit fdbce16 into develop Oct 15, 2025
105 of 109 checks passed
@chargome chargome deleted the cg-canary-next branch October 15, 2025 11:32
timfish pushed a commit that referenced this pull request Oct 15, 2025
next@canary now resolves to next 16 which is why we need to update the
testing strategy here
This was referenced Oct 15, 2025
This was referenced Oct 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.