Re: Query about failure of Debian 6 64 bit to swap properly
- To: debian-user@lists.debian.org
- Subject: Re: Query about failure of Debian 6 64 bit to swap properly
- From: Martin Steigerwald <Martin@lichtvoll.de>
- Date: Sun, 2 Sep 2012 21:29:07 +0200
- Message-id: <[🔎] 201209022129.07797.Martin@lichtvoll.de>
- In-reply-to: <20120829190128.GA7997@hysteria.proulx.com>
- References: <alpine.DEB.2.00.1208291605240.11791@bret-dd-workstation.busby.net> <alpine.DEB.2.00.1208300155260.18579@bret-dd-workstation.busby.net> <20120829190128.GA7997@hysteria.proulx.com> (sfid-20120829_232808_476112_79D9F42B)
Am Mittwoch, 29. August 2012 schrieb Bob Proulx:
> Then press F6 to change the sort function. Use the up and down cursor
> keys to select VIRT for sorting by size of virtual memory usage. What
> programs are the top virtual memory consumers on your system? (On
> mine it is usually firefox.) Based upon what those memory hogs are on
> your system we can advise what action might be taken.
No!
Virtual memory size does not say a single thing about real physical memory
usage.
An application can happily allocate 1 GiB or more of virtual memory
without every having the Linux kernel allocating physical memory at all
except for the management of the memory allocation at all.
Virtual memory is just address space. Unless the application writes to it,
the kernel does nothing, repeat, nothing in physical memory.
So its resident set size. And even that is not accurate, cause it usually
collects libary memory usage as well.
So when you have 100 processes using libc6 the library is still in memory
just once. So an approach is account to the process the resident set size
of the library divided by the amount of processes that use it.
In newer KDE versions the process monitor has a detailed memory statistics
page that does just that. I never have seen that in a shell command up to
know.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Reply to: