vmstat with the -n option would probably give more clear and pointed information about resource utilization (albeit not relative to any specific processes), if you're trying to see where you become swap-bound or disk-bound, etc. So "vmstat -n 5" in its own terminal...
lsof is another very useful tool, not sure if you've got it by default; but you can do simple piping such as lsof|grep firefox|wc -l to see how many handles firefox has open, for example. Maybe there are easier ways to do that, but that is how I learned. Agreed about Firefox not always closing out properly on linux, I find firefox-bin is the name of the process that hangs around most often, so killall helps there. I have not seen that problem much on Winders or Mac builds. Ben On Mon, Jan 24, 2011 at 1:17 PM, Horst <knoblauch137-0...@yahoo.com> wrote: > ... > > then start other apps, then firefox with increasing Tabs and demands. > > i.e. *before* you reboot, set firefox General to start with a blank page, > not to restore previous Tabs. > > You can also slow down top refresh to 5 sec or more for easier snapshots: > top -d 5 > > > - Horst > > _______________________________________________ > EUGLUG mailing list > euglug@euglug.org > http://www.euglug.org/mailman/listinfo/euglug >
_______________________________________________ EUGLUG mailing list euglug@euglug.org http://www.euglug.org/mailman/listinfo/euglug
