top | item 7353559

How to Profile a Leaky Sidekiq Job in Heroku

4 points| jkulmala | 12 years ago |happybootstrapper.com | reply

2 comments

order
[+] deedubaya|12 years ago|reply
We had good success with tracking down heroku memory leaks with Oink on a Rails4 ruby2.0 application. It turned out to be about 30% the code, 70% the defaults for the ruby2.0 garbage collector. Tweaking the default GC settings helped with most of our problem.
[+] jkulmala|12 years ago|reply
Thanks for letting me know. I'll take a look at that.