t consumes RAM specifically, not virtual memory in
general. Besides, from all I can see, the high memory usage is NOT
caused user space processes. So the output from ps was just to show that
even though some hundred MB of RAM (!) are used, just some few MB are
consumed by processes.
Kind regards
it required a debug version of the kernel (and that's
> unsuitable for just about anything short of kernel development).
By then I should probably go to debian-kernel? ;-)
Thanks again for all your help!
Martin
--
Martin Schwarz * Karlsruhe, Germany * http://kuroi.de/
Only I can't unload modules that are in use, of
course. Unloading vmw_balloon, vmw_vmci, and vmw_vsock_vmci_transport
didn't help.
> And that means - 'perf top', or better yet - 'perf record'.
I have never used perf before, will look into it.
Thanks a lot for your insight!
Martin
--
Martin Schwarz * Karlsruhe, Germany * http://kuroi.de/
Convert
lv_swap vg0 -wi-ao 2,00g
root@rad-wgv-srv01:~# lsmod | fgrep z
Module Size Used by
root@rad-wgv-srv01:~#
--------
--
Martin Schwarz * Karlsruhe, Germany * http://kuroi.de/
---
(any other commands I should repeat on the new system?)
Thanks
Martin
--
Martin Schwarz * Karlsruhe, Germany * http://kuroi.de/
Anything else I could check to help pinpoint the memory hog?
Thanks in advance!
Martin
--
Martin Schwarz * Karlsruhe, Germany * http://kuroi.de/
6 matches
Mail list logo