| |||||||||||||
I/O is the problem, not CPUI/O is the problem, not CPUPosted Nov 20, 2010 18:16 UTC (Sat) by mfedyk (guest, #55303)In reply to: I/O is the problem, not CPU by job Parent article: TTY-based group scheduling
I peg my cpu with firefox all of the time, and I have a dual core 64 bit cpu. firefox also manages to use all 4 gb and full up swap until I get my tab count down to about 200 or so.
btw, chrome does the same with memory at about 50 tabs...
(Log in to post comments)
|
|||||||||||||