"why is my Linux so damn slow?"
Michael Schwendt
mschwendt at gmail.com
Sat Feb 12 21:57:15 UTC 2011
On Sat, 12 Feb 2011 22:00:03 +0100, M. wrote:
> > A running Firefox, that displays an ordinary News website with several
> > animated GIFs and a couple of Flash ads, here increases the resched.interrupt
> > count by ~100 or more per second. After a few hours of uptime, that will
> > pile up, of course. Marko has quoted the uptime with his "top" output in
> > the blog post. To Marko, you can run
> >
> > watch -d1 cat /proc/interrupts
> >
>
> This is with Firefox running (right after "defragmenting" as suggested
> in the other post I just answered):
It isn't meant for posting it, but for monitoring the changes yourself.
Hence the -d (the '1' is a typo), which highlights the digits that change.
(watch -n1 -d cat /proc/interrupts)
> Every 2.0s: cat /proc/interrupts Sat Feb 12 21:58:15 2011
>
> RES: 8094091 8916019 Rescheduling interrupts
> This is right after killall firefox:
>
> Every 2.0s: cat /proc/interrupts Sat Feb 12 21:59:37 2011
>
> RES: 8101319 8924946 Rescheduling interrupts
So, for the 2nd cpu, it incremented by 8019 in roughly more than a minute,
which is between 100-200 per second. That's also what other people
experience without any unusual slowness of the system. Though, when you've
stopped Firefox, does the interrupt count still increase so quickly? And
with Firefox not being busy anymore (and not processing Flash), are your
troubles during typing words and sentences cured or not?
More information about the users
mailing list