 |
Forums |
Admin Discussion Forums: help Start New Thread
By: Piotr Szotkowski
RE: Memory leaks with ruby-prof 0.6.0 on Ruby [ reply ] 2009-11-21 13:07
|
I’m not 100% sure whether there’s a single answer, but I’d go with ‘yes’.
The problem of using ruby-prof on 1.9 is that the svn checkout does not work (requires a patch from the Redmine), and there are two GitHub forks: one does not aggregate the calltree results (so you end up with thousands of entries like Set#&-1138), while the other takes incredible amount of time to aggregate the results (like 50x runtime).
|
By: Piotr Szotkowski
RE: Memory leaks with ruby-prof 0.6.0 on Ruby [ reply ] 2008-04-12 19:29
|
I just ran some more tests and it seems the leak is most probably in Ruby itself: Ruby 1.9.0-0 leaks very much in comparison to Ruby 1.8.6p111 running the same script.
I’ll test with Ruby 1.9.0-1 in the coming days and report back (but it’s most probably not a ruby-prof issue).
|
By: Piotr Szotkowski
Memory leaks with ruby-prof 0.6.0 on Ruby 1.9 [ reply ] 2008-02-14 18:28
|
(This is a repost from ruby-talk – I didn’t get any replies there, unfortunately.)
I’m running into memory leaking issues when trying to profile my code with ruby-prof 0.6.0 on Ruby 1.9. Two scenarios, in which 1.8 is Ubuntu’s packaged Ruby 1.8.6.p111, while 1.9 is hand-compiled Ruby 1.9.0.r14709. ruby-prof 0.6.0 from RubyGems in both cases. Memory usage reported with the proprietary, highly scientific method of Looking at Live Htop Changes in Memory Usage for the Whole System™. Times are time’s real/user, the ruby-prof’s printer is graph_html.
Ruby 1.8:
* the code ran with plain Ruby executes in 1m41s/1m22s, the memory consumption stays below 300 MiB.
* the code ran with ruby-prof executes in 4m35s/2m49s, the memory consumption stays below 320 MiB.
Ruby 1.9:
* the code ran with plain Ruby executes in 0m30s/0m30s, the memory consumption stays below 310 MiB.
* the code ran with ruby-prof executes in… well, I stopped the execution when the memory consumption passed my laptop’s 1 GiB and made a 350 MiB dent at my temp partition.
Are there any known memory issues with ruby-prof 0.6.0 on Ruby 1.9?
Unfortunately, the code under profiling being the code behind my PhD, I can’t currently open source it (I will once my research is complete); I can send it to people off-list (provided it doesn’t get shared further).
Thanks in advance for any comments/ideas.
|
|
 |