Re: Audio processing thread realtime priorties
Re: Audio processing thread realtime priorties
- Subject: Re: Audio processing thread realtime priorties
- From: Jeff Moore <email@hidden>
- Date: Thu, 11 Jun 2009 20:56:07 -0700
Sort of. It really depends on whether the data dependencies in the
rendering engine actually allow for significant chunks to run in
parallel. One thing to consider here is that managing a worker thread
incurs some overhead in terms of management and and rendez-vous with
the IO thread.
Generally, the amount of extra work you can do does not scale linearly
with the number of threads/cores involved. Plus, the quantum of work
done on each thread has to be sufficiently large enough to be worth
the overhead as well.
On Jun 11, 2009, at 6:26 PM, Jeremy Sagan wrote:
On Jun 11, 2009, at 5:53 PM, Jeff Moore wrote:
That said, using a worker thread might not help either. This
doesn't magically make the deadline softer or give you any more
time to do the work. You will still be held to meeting the same
deadlines.
Accept that, as I understand it, the worker thread can run
simultaneously as the audio thread on a separate processor on a dual
CPU machine and this may buy you more time.
--
Jeff Moore
Core Audio
Apple
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden