You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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:
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?
The text was updated successfully, but these errors were encountered: