site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Am 16.12.2005 um 15:06 schrieb Stéphane Letz: The spikes are probably too short to be seen by you/your tool. Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... We are debugging a strange issue with abnormal CPU spikes occurring in a test application. CPU spikes are perfectly normal. If you start some calculation, the CPU runs 100%, until done. If you do a short calculation, you get a spike. Anything else would be a waste of time without a benefit. The question you're after is probably, how are other tasks/apps/ threads affected by your app. This is where scheduling policies jump into the picture. On 10.4.3, the average CPU use on a dual G5 is now 0.6 %, but there is no more CPU spike .... This email sent to site_archiver@lists.apple.com