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

Possible Memory leak #52

Open
jwoertink opened this issue Oct 26, 2023 · 0 comments
Open

Possible Memory leak #52

jwoertink opened this issue Oct 26, 2023 · 0 comments

Comments

@jwoertink
Copy link

We have been using v0.4.0 in production since the release. When we try to update to the latest main commit, our app tanks.

image
image

These are graphs from our app showing memory use (top) and CPU use (bottom). The crazy spikes is when we deployed main , then after reverting back to v0.4.0 you can see where the app calmed down. We made no other changes for this deploy.

#48 is also somewhat related. Originally our app was getting DB::ConnectionRefused errors locally when pulling in the latest commit, but we made changes to our app which seemed to resolve that issue by just adding max_pool_size=170 to our postgres connection url.

I'm guessing on v0.4.0 there may also be a leak, then with d43a6a1 this was exposed a lot more by sending the calls in concurrently.

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

No branches or pull requests

1 participant