Date: | Mon, 30 Nov 2009 07:59:19 -0600 |
---|---|
From: | Dan Gibson <degibson@xxxxxxxx> |
Subject: | Re: [Gems-users] Does ruby leak memory? |
Javier, Having made that same graph on a couple of occasions myself, I can say with some confidence that this is correct behavior, and not a leak. The phenomenon you're observing is an artifact of how Ruby implements 'arbitrary' coherence. Whenever a memory block is accessed for the first time, a directory entry is allocated for that line, which will be used to track some state relating to this block (see your protocol's Directory_Entry). This happens in DirectoryMemory::lookup. These blocks are never reclaimed. Therefore, Ruby's memory allocation can continue to grow until the target system has accessed every block in its available memory. I see in your post that you are using an application with a fixed working set. After touching all of it, I would expect memory usage to plateau for the most part, except for other system activity, a behavior that I have seen myself -- it also seems to happen at about X=800M cycles in your graph. Bear in mind that even a 'controlled' application isn't the only thing running on a full-system simulator, and Ruby's memory will still grow, inexorably, due to system activity and interference from other processes. However, just to cover all our bases, try running Ruby's tester. Ruby's tester limits the number of actually addresses used to a handful, so the memory footprint should be more stable. Even then, I wouldn't be surprised if you still saw some inflation due to stats gathering (e.g., some maps in Profiler.C). Regards, Dan 2009/11/30 Javi Merino <jmerino@xxxxxxxxxxxxx> Hi, when we run long simulations using GEMS+Simics, we get a very big -- http://www.cs.wisc.edu/~gibson [esc]:wq! |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | [Gems-users] Does ruby leak memory?, Javi Merino |
---|---|
Next by Date: | Re: [Gems-users] Collecting Ruby stats for TM, Jayaram Bobba |
Previous by Thread: | [Gems-users] Does ruby leak memory?, Javi Merino |
Next by Thread: | [Gems-users] Failing to make Ruby, Jiří Šimša |
Indexes: | [Date] [Thread] |