You are not logged in.
Pages: 1
Arrghhhh. I had a picture perfect post that strictly adhered to forum etiquette and then firefox crashed on me and I have to start from scratch! What a pisher. Please accept my advance apologies if my second attempt is not quite as pristine and detailed as the first. I ask in advance to please take it easy on me. I am very new at this and spent a great deal of time doing my homework and searching various forums before posting. I
Basically, I have three computers with Arch installed, two of them i686 and one x64. I am running Gnome + Compiz on all three. The x64 has 6GB of RAM. I am usually just running firefox on top of gnome+compiz. This machine starts out a boot at 200MB of RAM and then fluctuates betweekn 200-650MB for the first few hours. Then, out of nowhere, it will jump up to a steady 1.8GB of RAM and just sit there. I am aware that Linux caches RAM for faster access and that it is not "eating" this memory. I am just curious why it happens only on this one machine and none of the others. Is it related to x64?
Thanks in advance.
Archieman
A good solution applied with vigor now is better than a perfect solution applied ten minutes later. - George S. Patton
Offline
Not normal. I have an x86_64 box with 8 gigs, gnome+compiz and it never goes that high unless I'm taking up space in /dev/shm or running vbox. Add this to your ~/.bashrc and when the mem usage spikes, run the function and post the output.
% which memrss
memrss: aliased to ps -eo comm,pmem,rss,etime --sort -rss | numfmt --header --from-unit=1024 --to=iec --field 3 | column -t | head -n20
Here is an example output from my machine:
$ memrss
COMMAND %MEM RSS ELAPSED
deluged 1.9 626M 01:31:17
Thunar 0.6 214M 05:14:19
xfdesktop 0.6 194M 05:14:19
deluge-gtk 0.3 113M 58:03
Xorg 0.2 87M 05:14:24
xfwm4 0.1 57M 05:14:19
panel-10-weathe 0.1 53M 05:14:19
xfce4-panel 0.1 40M 05:14:19
panel-7-pulseau 0.1 38M 05:14:19
xfce4-terminal 0.1 38M 00:02
xfce4-session 0.1 34M 05:14:19
panel-8-actions 0.0 28M 05:14:19
tumblerd 0.0 28M 00:58
systemd-journal 0.0 27M 01:43:27
panel-9-xfce4-s 0.0 26M 05:14:19
panel-14-netloa 0.0 25M 05:14:19
panel-4-datetim 0.0 25M 05:14:19
xfce4-screensav 0.0 25M 05:14:19
python 0.0 23M 04:59:19
Now you can see what the hell is taking up the memory.
Last edited by graysky (2020-12-06 20:31:39)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Pages: 1