Hacker News Reader

Sentry is great but I’ve noticed that it significantly increases the request response time which makes it unusable for high traffic web apps. This happens with both the hosted and self-hosted instances. I’m not sure if it’s due to bad configuration or PHP. I’ll give this a try and see…

View on HN

This is due to how PHP and Sentry for PHP works. It sends out the data after every request to Sentry backend via HTTP. Depending on your network path to their servers, I have seen this take 10-100ms. This is different on how other APMs work for PHP, for example Tideways that I work on, or DataDog/NewRelic/Blackfire. They have a local agent running that accepts the data over socket/tcpip before sending it to the backend for processing.

The workaround in case of Sentry is to deploy the Sentry Relay in your network and send all data there.

Depending on PHP Sentry client version,

Sentry client v1 (Raven_Client) you can configure the client in different send modes (curl_method), sync (default), async (curl_multi), exec (fork)

https://docs.sentry.io/clients/php/config/

For Sentry client v2 I think you need to configure the Transport layer to use async

https://docs.sentry.io/platforms/php/configuration/transport...

Reply on news.ycombinator.com