Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author stayallive

    (@stayallive)

    It depends ??

    If you only use the PHP error tracking the impact (unless you have errors to report) is negligible. When reporting errors to Sentry it does cause a slow down (sending the error) which could be mitigated by using Relay (https://docs.sentry.io/platforms/php/performance/#improve-response-time).

    The JavaScript/Browser story is more complicated. You are (depending on the features you enabled like performance) loading a sizeable JavaScript bundle. The impact of this bundle varies and is best to test and validate what the impact is.

    I know this is not a clear cut answer but hope it shines some light and helps you figure out what is applicable to you and helps you test how the impact in your situation is.

    Hi!

    A bit curious if this also resolves bad performance, if sentry becomes unavailable. I had an issue where sentry went offline, and my site became very slow. I believe that this is due to some timeout in the requests.

    Thanks!

    Plugin Author stayallive

    (@stayallive)

    The number of errors sent per request makes the impact. It is not expected to sent multiple errors per request to Sentry, most of the requests shouldn’t sent any so if the case is that Sentry becomes unavailable the timeouts (which have been re-adjusted couple of times in the past months) should prevent any major slowdowns but when Sentry is reporting multiple errors per request this can stack up quickly.

    However if you want to be sure you can use Relay to solve that problem completely since Relay will accept events even if Sentry is not available and wait for Sentry to become available to sent events so as long as Relay is online your application can send it’s errors quickly.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WordPress Site Performance’ is closed to new replies.