- edited description
Don't create a new manager on each request
Issue #1
resolved
Our servers had error spike, due to which they tried to send many errors via raven, but this brought them quicly to eat more and more RAM which wasn't freed. I'm not 100% sure what happened, but one mis-behavior which seems clear is that this raven client is creating a new manager on each operation (0), which is quite a heavy operation.
This mis-behavior is not easy to spot. I propose that you require a manager to be passed upon initialization to ensure this doesn't bring problem for other users.
Thank you!
Comments (3)
-
reporter -
repo owner - changed status to resolved
Add
sendRecordWith
HTTP transport variantIt uses external HTTP Manager to save resources.
(Fixes
#1)→ <<cset 838c38e20e19>>
-
reporter Thank you!
- Log in to comment