We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have an update for our Django Integration to generate spans that will show up in the "Cache Module" of the Sentry Performance tab.
I did some load testing, to get a feel how much overhead we are putting on our Users Servers.
The project used for load testing can be found here: https://github.com/antonpirker/testing-sentry/tree/main/test-django-cache-module (In the /reports folder are the results of my test)
/reports
The text was updated successfully, but these errors were encountered:
This is the baseline, running the load test without Sentry:
This is the test with Sentry but without any cache spans:
This is the test with Sentry and with cache spans but without cache item sizes:
This is hte test with Sentry, with cache spans, and with cache item sizes:
Sorry, something went wrong.
Test case 1 (with Sentry but without cache spans) has a way higher memory usage than test cases 2 and 3!?
I repeated the test case 1 twice and it showed basically the same result (Can be found in the /reports).
antonpirker
No branches or pull requests
We have an update for our Django Integration to generate spans that will show up in the "Cache Module" of the Sentry Performance tab.
I did some load testing, to get a feel how much overhead we are putting on our Users Servers.
The project used for load testing can be found here:
https://github.com/antonpirker/testing-sentry/tree/main/test-django-cache-module
(In the
/reports
folder are the results of my test)The text was updated successfully, but these errors were encountered: