Content-Length: 286458 | pFad | http://github.com/getsentry/sentry-javascript/issues/16825

30 [Next.js] Frontend Performance Issue After Adding Sentry · Issue #16825 · getsentry/sentry-javascript · GitHub
Skip to content

[Next.js] Frontend Performance Issue After Adding Sentry #16825

Open
@dalnoki

Description

@dalnoki

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/browser

SDK Version

9.33

Framework Version

Next.js v15.3.2

Link to Sentry event

No response

Reproduction Example/SDK Setup

Additional details here.

Steps to Reproduce

After integrating Sentry’s Next.js They into their frontend, a customer experienced that their /login route response time increased from ~2 s to ~13 s. We are currently sending a small percentage of transactions (via tracesSampleRate: 0.05) and have Session Replay enabled. They confirmed that the slowness issue goes away when Sentry is disabled.

Expected Result

Minimal performance degradation

Actual Result

The load time is significantly higher than before adding Sentry

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions









      ApplySandwichStrip

      pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


      --- a PPN by Garber Painting Akron. With Image Size Reduction included!

      Fetched URL: http://github.com/getsentry/sentry-javascript/issues/16825

      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy