Thanks for blogging this. Today I had my Account manager and another support person from Heroku pushing me to add that experimental feature, so I could see the memory usage of our dynos. I had reported on twitter and in a support ticket that the memory reported by newRelic didn't match the values that our Account Manager sent me. He sent me this because we were trying to add 4 Unicorn processes to a 1 Gig Dyno, and newRelic was reporting our app never went over 256MB. Our Account manager sent a different trace of memory usage.
I have lost all faith in the values that newRelic reports that come from Heroku.
Comments
Thanks for blogging this. Today I had my Account manager and another support person from Heroku pushing me to add that experimental feature, so I could see the memory usage of our dynos. I had reported on twitter and in a support ticket that the memory reported by newRelic didn't match the values that our Account Manager sent me. He sent me this because we were trying to add 4 Unicorn processes to a 1 Gig Dyno, and newRelic was reporting our app never went over 256MB. Our Account manager sent a different trace of memory usage.
I have lost all faith in the values that newRelic reports that come from Heroku.
log-runtime-metrics does work -- just enable it for a half hour or so, observe the stats, then turn it off. Just can't keep it running long-term.