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

oversized prepared statements cache #594

Closed
mooreniemi opened this issue May 7, 2015 · 1 comment
Closed

oversized prepared statements cache #594

mooreniemi opened this issue May 7, 2015 · 1 comment
Labels

Comments

@mooreniemi
Copy link

While running in production, we're seeing our memory flood with T4CPreparedStatements. They end up taking 90% of heap when we look at the dump. I was hoping you could help me rule out any issues in OE.

I saw in other DB adapters some rescue protection not present in OE, ie:

begin
  @connection.prepare nextkey, sql
 rescue => e
   raise translate_exception_class(e, sql)
end

I also saw issues even with even the above protections when Rack::Timeout is used (as it is for us in our Rails stack): rails/rails#17607

Any ideas why I'd be getting overrun by T4Cs?

@stale stale bot added the wontfix label May 8, 2017
@stale
Copy link

stale bot commented May 8, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot closed this as completed May 15, 2017
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

1 participant