Hello,
after reading a LWN article I started playing with the "memory
ovcercommit" switch on a Linux box. Later I wondered why I wasn't
unable to run FG reliably anymore and ran a 'top' to see what's going
on here. I noticed that FG appears to lock huge amounts of memory - and
the X server as well.

Can anyone confirm similar experience ?

top - 14:09:04 up 23:12,  2 users,  load average: 1.10, 0.40, 0.14
Tasks: 137 total,   2 running, 135 sleeping,   0 stopped,   0 zombie
Cpu(s):  82.8% user,  17.2% system,   0.0% nice,   0.0% idle,   0.0% IO-wait
Mem:    513644k total,   510292k used,     3352k free,    58532k buffers
Swap:   265064k total,      200k used,   264864k free,   131260k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                
 6127 mas       25   0  583m 173m 275m R 93.1 34.6   0:49.44 fgfs
 6180 mas       15   0  583m 173m 275m S  4.3 34.6   0:00.79 fgfs
  969 root      15   0  325m  57m 270m S  2.3 11.5  10:20.58 X
[...]


Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to