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.
Hum... It seems you've not really read/understood my mail...
The thread that show this behaviour is a real-time (time-constraint)
priority 97, and in the test applications (the *simplest* code i had
to show the problem) does nothing more that rescheduling itseld the
next millisecond. Thus it normal bahaviour is to consume almost 0%
The real application does *something* in its real-time thread, but
its timing get disturbed when the CPU spike (which last several
second) occurs.
Regards
Stephane Letz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
