-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Laravel note on performance overhead potentially misleading #11337
Comments
Assigning to @getsentry/support for routing ⏲️ |
We got PR open at #11533. I just want to make sure that we fully understand how our SDKs work. Just because an SDK uses an async transport, it does not mean that the overhead magically disappears. |
yes, also 'overhead' is not very precise, the answer is different depending on what you mean by it :)
curious why is SDK overhead a bigger problem when developing or testing rather than production? I understand you want quick local iterations but still there's something off in that logic... |
SDK
PHP SDK
Description
https://docs.sentry.io/platforms/php/guides/laravel/#local-development-and-testing
Mentions negative effect of Sentry SDK on performance. I believe it may be a bit misleading
Context: this section seems to be picked up a lot by RAG as it matches certain use cases well and other platforms don't have an equivalent doc. It's on RAG that it wasn't able to tell it's SDK-specific, but maybe we can meet it halfway? 🙂
Suggested Solution
add something along the lines of "because PHP unlike other platforms doesn't have background threads"? (@cleptric correct me if this is wrong please)
The text was updated successfully, but these errors were encountered: