[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sc-dev] idle scsynth CPU usage
I ran Shark, and the difference came in the scsynth process, under
the thread CAPThread. On the old machine, this was running at about
1%, on the new one, about 8%
Does this ring any bells with anyone? Since Nicholas also mentioned
the same performance issues with the same PB in the series, does
anyone think this is something that can be fixed in SC (not saying
necessarily that SC is the problem)... or is it something that is
just a problem with the new machines that may warrant some discussion
with Apple about a return... Most of this seems to be involving the
com.apple.driver.AppleDBDMAAudio and the
com.apple.iokit.IOAudioFamily libraries. The saved session is rather
large (1.2 MBs), but if anyone is interested in the data collected,
let me know and I can e-mail it off.
Post-Doctoral Research Associate - Center for Digital Arts and
Raitt Hall - University of Washington
Seattle, Washington 98195
On Jan 8, 2006, at 9:31 AM, chris clepper wrote:
On 1/8/06, Joshua Parmenter <joshp@xxxxxxxxxxxxxxxx> wrote:
ick... I don't know how to even phrase this when calling Apple.
If James McCartney is listening... any suggestions?
Download the CHUD tools from here:
http://developer.apple.com/tools/download/ which requires a free
developer registration. The app you want to run is called Shark and
it profiles any application or the entire system. This is a quick
primer on how to use it:
Compare runs between the new machine and an old one and that should
reveal a clue or two about what is taking up the extra time.
sc-dev mailing list