Performance Issue for NestJS Project with Sentry Performance Enabled

[ReneGreen27]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/browser

SDK Version

9.5.0

Framework Version

NestJS

Link to Sentry event

No response

Reproduction Example/SDK Setup

Mini repro app and details regarding performance included in internal ticket #146790

Steps to Reproduce

clean NestJS framework + Sentry. The route for testing simply returned a small JSON text.

According to the measurement results:

Clean framework without Sentry - 30,000 rps, 3ms average response time.

Clean framework + Sentry - 2,500 rps, 39ms average response time.

I used the following Sentry configuration:

Sentry.init({
  dsn: '',
  defaultIntegrations: false,
  integrations: [
  nodeProfilingIntegration(),
  Sentry.nestIntegration(),
  Sentry.httpIntegration(),
  Sentry.onUncaughtExceptionIntegration(),
  Sentry.onUnhandledRejectionIntegration(),
  ],
  environment: 'local',
  tracesSampleRate: 1,
  profilesSampleRate: 1,
});

Reducing the values of tracesSampleRate and profilesSampleRate to 0.1 slightly improves the situation

main performance loss occurs due to the Sentry.httpIntegration() module

Expected Result

Not impactful to app performance to have sentry performance enabled

Actual Result

Performance affected

[andreiborza]

Thanks for the easy to follow reproduction repo. Can confirm, I'm observing the same outcomes with the http integration added as the only integration. I also tried production mode with the same results.

When only using the httpIntegration and disabling everything that's configurable inside it, I got up to 27k rps and 3ms avg response time on my machine. As a baseline I'm getting 85k rps tho.

Sentry.httpIntegration({
   breadcrumbs: false,
   spans: false,
   trackIncomingRequestsAsSessions: false,
   disableIncomingRequestSpans: true,
}),

cc @chargome @mydea

[chargome]

Hey @ReneGreen27, we have several PRs in place that should slightly improve performance, but generally the instrumentation will cause some overhead. Current recommendation is to use the setup posted above by @andreiborza and update to latest versions as we'll try to further optimize this.