pgm memory usage

rikona rikona at sonic.net
Fri Nov 5 07:01:08 UTC 2010


Hello Rashkae,

Thursday, November 4, 2010, 6:56:57 PM, Rashkae wrote:

R> On 10-11-04 09:18 PM, rikona wrote:
>> I have about 10 copies of konq open on all the desktops. Three of them
>> are using about 30% of memory. They are all being used to see dir
>> listings - none are on the net. Also have 10 'opera' browsers running,
>> using 50+% of mem, and I'm getting swap issues[~80-90% of swap is
>> used]. Switching pgms is quite slow. Is there a way to tell which
>> copies, **in the GUI**, are using how much memory, or, alternatively,
>> can I get the PID for a *particular* pgm in the GUI?
>>
>> thanks,
>>
>>      rikona
>>    


R> I'm afraid that when you are dealing with a shared Library / Shared
R> Memory / demand paging Operting system (like any of the modern
R> desktop OS's), determining memory usage of individual windows is
R> close to impossible.

That's what I thought might be the case, given the lack of 'how tos'
for doing it.

R> It's doable, but it's a very black art, and certainly not something
R> that can be done from within a GUI.

CLI is OK, but the black art part is rather worrisome. :-)

R> However, for the purpose of troubleshooting Memory starvation
R> issues, here is my favorite 'trick,'. It doesn't give you
R> scientific measurements, but will point you in the direction you
R> want to solve your workload issues.

R> Issue command in a terminal window:
R> cat /proc/meminfo | grep Commited

R> that should show you your "Committed_AS" value. This is what you
R> want to reduce, ideally, for best performance, you want this to be
R> less than your physical ram, though that's not always possible on
R> low memory systems.

From htop, I can already see physical ram is full, and swap is 80-90%
full.

R> Try closing some windows, and check the command again at each one.
R> I think you'll find that the Konq windows take up very little
R> (unless you close all of them)

That's what I wanted to do, to free up memory space - the question was
WHICH one to close first. The mem usage of the different konq
instances is QUITE different, with some konq instances taking LOTS o
memory, and others taking little. I was hoping to be able to close
the BIG ones first.

The opera instances all take the same [relatively large] amount, for
some reason I don't understand - the numbers and types of open tabs is
rather different in the different instances. I tried reducing a couple
to only one very simple tab open, but that did not seem to reduce the
mem for ANY copy of opera.

Thanks much for the reply and help,   

-- 

 rikona        





More information about the ubuntu-users mailing list