iTunes CPU use

Happened to me as well.

CPU usage is fine for me
When it is playing a song it is between 1-5%
When clicking to the next song it goes up to between 25-40%, but comes back down immediately.

When it is ripping a cd it is up in the 90's which is horrible.

nightfly is right on this.

The first time software comes out it can be a bit hairy. CPU intensive and all that. I'm sure there will be several updates.

Originally posted by ToddW
nightfly is right on this.

The first time software comes out it can be a bit hairy. CPU intensive and all that. I'm sure there will be several updates. No no, when he says it's a one-time thing, he means once when you first import your library into iTunes, not first version of the software. If you have "Soundcheck" turned on in the prefs, it has to analyze all your songs as you import them, which takes a lot of resources, but when it's done, it's done. Just for reference it uses between 5% and 15% for playback on my 800 MHz Mac, but never more than that, and pretty much 0% when idle.

Originally posted by HiRez
No no, when he says it's a one-time thing, he means once when you first import your library into iTunes, not first version of the software. If you have "Soundcheck" turned on in the prefs, it has to analyze all your songs as you import them, which takes a lot of resources, but when it's done, it's done. Just for reference it uses between 5% and 15% for playback on my 800 MHz Mac, but never more than that, and pretty much 0% when idle.

Does soundcheck alter the music file itself or just normalize it when it plays in iTunes or is synced to the 'Pod?

Originally posted by HiRez
No, the music is not altered on the disk, the volume is adjusted during playback, like the EQ.

Cool, thats what I thought.

Thanks

Sure, it will generally use all available CPU cycles it can while it's encoding, as it should. But, that shouldn't have anything to do with your dialup connection getting dropped. If it does, you should look at perhaps your modem drivers...or something. iTunes or any other app should be able to ask for 100% of the available cycles and not kill anything else. The OS should dole out as many CPU cycles as requested by any apps that ask, if it decides it can spare them. Having your CPU use near 100% usage is a good thing generally.

Originally posted by HiRez
The OS should dole out as many CPU cycles as requested by any apps that ask, if it decides it can spare them. Having your CPU use near 100% usage is a good thing generally.

I have been in IT for a long time and one thing I know is 9 times out of 10 if the CPU of any machine, especially a server, is pinned at 100% it is usually indicative of a problem (poorly written app, process stuck in a loop, etc...) and performance suffers.
That is certainly the case with those experiencing a lag in their PC's performance due to iTunes strain on the proc.

You are correct that it should be the job of the OS to regulate how many cycles are divided among which app, but when the CPU is unable to successfully to do so it is usually indicative of a problem on the application layer.

Originally posted by HiRez
Mmm yes, I was referring specifically to long-form situations where CPU saturation is appropriate, eg. MP3 or MPEG encoding, 3D rendering, running simulations, SETI@Home, etc.

Very true, maximizing CPU cycles is appropriate when performing certain functions such as burning, encoding, compiling, and in the case of Seti when you allow it to use all available cycles. I think the problem for many occurs with iTunes just being open. Having an application running should never continually pin a proc and this is indicative of some issue or conflict in the software.