Skip to content
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

Investigate PostgresIntegration for Memory issues #12243

Closed
Tracked by #12242
AbhiPrasad opened this issue May 27, 2024 · 2 comments
Closed
Tracked by #12242

Investigate PostgresIntegration for Memory issues #12243

AbhiPrasad opened this issue May 27, 2024 · 2 comments
Assignees
Labels

Comments

@AbhiPrasad
Copy link
Member

AbhiPrasad commented May 27, 2024

We've gotten two different reports (#11897, https://discord.com/channels/621778831602221064/1242436171737333810) that using the postgres integration with Sentry is causing memory issues.

Let's investigate this further.

@timfish
Copy link
Collaborator

timfish commented Sep 24, 2024

I conducted some testing of the pg instrumentation in isolation with Postgres 13.14 with many thousands of transactions per second and both CPU and memory seem roughly similar and there were no timeouts.

The only changes to the otel instrumentation over the last year have been a couple of small PRs to reduce allocations.

@AbhiPrasad
Copy link
Member Author

Maybe these OTEL upstream changes have helped. Let's close this for now then and also close #11897. We can create another issue if we get another reproduction. Thanks for taking a look @timfish!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants