Date: Tue, 20 Jul 2010 23:50:28 -0700 (PDT) From: Doug Barton <dougb@FreeBSD.org> To: Dan Nelson <dnelson@allantgroup.com> Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-current@freebsd.org, Rui Paulo <rpaulo@freebsd.org> Subject: Re: Why is intr taking up so much cpu? Message-ID: <alpine.BSF.2.00.1007202342350.1717@qbhto.arg> In-Reply-To: <20100720164600.GA85770@dan.emsphone.com> References: <F653FF83-D9CF-42A2-AE9A-B8F914090065@FreeBSD.org> <alpine.BSF.2.00.1007171208010.1538@qbhto.arg> <20100717192128.GM2381@deviant.kiev.zoral.com.ua> <alpine.BSF.2.00.1007180113370.1707@qbhto.arg> <20100718103003.GO2381@deviant.kiev.zoral.com.ua> <4C43541C.3060101@FreeBSD.org> <20100718194109.GU2381@deviant.kiev.zoral.com.ua> <4C435CBE.50500@FreeBSD.org> <20100718202338.GI5485@dan.emsphone.com> <alpine.BSF.2.00.1007192259170.1725@qbhto.arg> <20100720164600.GA85770@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 20 Jul 2010, Dan Nelson wrote: > In the last episode (Jul 19), Doug Barton said: >> On Sun, 18 Jul 2010, Dan Nelson wrote: >>> You can also use dtrace to get a count of callouts and their time spent. >>> Run this for a few seconds then hit ^C: >> >> Okey dokey, here you go: >> >> http://people.freebsd.org/~dougb/normal-dtrace.txt >> http://people.freebsd.org/~dougb/bad-dtrace.txt > > I don't see any real difference between those two runs, so maybe it's not a > callout eating your CPU. How about running this for a few seconds, which > will print all the stack traces seen during the sampling period: > > dtrace -n 'profile:::profile-276hz { @pc[stack()]=count(); }' > > On an otherwise idle system, you should see most of the counts in cpu_idle, > with the remainder clustered in whatever code is eating your CPU. Ok, here's the output from the above: http://people.freebsd.org/~dougb/normal-dtrace-2.txt http://people.freebsd.org/~dougb/bad-dtrace-2.txt FYI, I updated to r210317 because mav's latest commits are clock related, and it seemed to help. The first flash video I tried to watch went all the way through and afterwards intr was around 2% cpu (normally it's in the 0.n% range). However, after killing all the stray npviewer.bin processes, and killing firefox, it went back down. It took watching several videos in a row to get it to the point where intr started running away again. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1007202342350.1717>