View Single Post
pichlo's Avatar
Posts: 6,450 | Thanked: 20,983 times | Joined on Sep 2012 @ UK
#15
Your 'free' output looks OK. Swap is barely used. I assume you are not experiencing any problems now, are you?

A more interesting of the 'top' output would be the following few lines, like this:
Code:
Mem: 229072K used, 6180K free, 0K shrd, 43144K buff, 46060K cached
CPU:  2.5% usr  5.3% sys  0.0% nic 89.4% idle  2.5% io  0.0% irq  0.0% sirq
Load average: 0.09 0.08 0.07 1/205 4629
  PID  PPID USER     STAT   RSS %MEM %CPU COMMAND
 4280  1191 user     S    16624  7.0  0.4 /usr/bin/modest
 4193  1461 user     S    14756  6.2  0.0 /usr/sbin/browserd -s 4193 -n browseru
 1029   703 root     S <  11356  4.8  0.2 /usr/bin/Xorg -logfile /tmp/Xorg.0.log
 1303  1191 user     S    10564  4.4  0.7 /usr/bin/hildon-home
 1805  1191 user     S     9128  3.8  0.0 /usr/bin/browser
 4434  1191 user     S     9128  3.8  0.0 /usr/bin/osso-xterm
The answer to your question 5 is, "it depends". If the real problem is that all your virtual memory is used up, then resetting swap is not going to help. That's where 'free' comes in. If, OTOH, some runaway background task allocated a lot of memory that got swapped out in a hypothetical situation such as what I described, then we need to find the culprit. Hence 'top'.
 

The Following User Says Thank You to pichlo For This Useful Post: