Tuesday, February 3, 2015
On Tuesday, February 3, 2015 at 3:07:38 PM UTC, antgel wrote:
Are there any practical solutions to better-understanding what makes these actions grow the heap so much, apart from staring at the code? We feel we lack data / visibility in order to make improvements. Please let me know if this is too vague, and if more details can help provide better responses from the list.
I had to track down an issue like this recently and found rack-mini-profiler very useful - as well as the sorts of numbers you already have it can print out how many objects of each class were allocated this request and in total - this sometimes helps pin down what is being leaked
Fred
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/77c6a860-1c9c-47dd-93c9-ad7584873f39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment