http://www.ruby-forum.com/topic/126187 presents ‘dike’ which tells you where each memory object is created.
Presents a memory profiler.
If you run ruby-prof it can also work for rails (has its own plugin for your rails app).
Also if you patch your ruby it can tell you object allocations per function call.
http://scottstuff.net/blog/articles/2006/08/17/memory-leak-profiling-with-rails is an object counter (once every x seconds dumps to disk how many of each object exist). To make it work copy and paste the code to a file, require it, then run MemoryProfiler.start and it will dump a memory ‘overview’ ever 10 s to disk.
http://www.ruby-forum.com/topic/126187 presents ‘dike’ which tells you where each memory object is created.
Presents a memory profiler.
If you run ruby-prof it can also work for rails (has its own plugin for your rails app).
Also if you patch your ruby it can tell you object allocations per function call.
http://scottstuff.net/blog/articles/2006/08/17/memory-leak-profiling-with-rails is an object counter (once every x seconds dumps to disk how many of each object exist). To make it work copy and paste the code to a file, require it, then run MemoryProfiler.start and it will dump a memory ‘overview’ ever 10 s to disk.