How to Profile a Leaky Sidekiq Job in Heroku(happybootstrapper.com)
happybootstrapper.com
How to Profile a Leaky Sidekiq Job in Heroku
http://www.happybootstrapper.com/2014/profile-leaky-sidekiq-job-heroku/
1 comments
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.
Thanks for letting me know. I'll take a look at that.