Re: Pinning IO Thread to a particular processor
Re: Pinning IO Thread to a particular processor
- Subject: Re: Pinning IO Thread to a particular processor
- From: email@hidden (Stefan Haller)
- Date: Wed, 8 Feb 2006 18:28:25 +0100
- Organization: Ableton
Stefan Haller <email@hidden> wrote:
> Jeff Moore <email@hidden> wrote:
>
> > It tells me that your IOProc is right out there on the edge of using
> > all the available time in these cases. I'd be very curious to see how
> > these compare to the cycles that don't overload.
>
> I'm not at the office tomorrow; I'll try to collect some more data on
> Friday.
OK, it took me some more time. I hope you still remember what this was
about. :-)
I have put a couple of new screenshots on my web site.
<http://home.snafu.de/stk/tmp/1_CPU.png> shows the telemetry window with
only 1 active CPU. I didn't get any overloads this time.
<http://home.snafu.de/stk/tmp/4_CPUs_Overview.png> shows the telemetry
with 4 active CPUs.
<http://home.snafu.de/stk/tmp/4_CPUs_Detail.png> shows the same, but
with some of the entries expanded. (It would really help to be able to
save and load logs, like in Shark...)
<http://home.snafu.de/stk/tmp/HALLab_Latency_Trace.txt> is the latency
log that was taken at the 4 CPU test.
To recap, the test document was a Live set that created about 77% audio
load, buffer size was 128 frames, using built-in audio.
Let me know what other information I can provide to help track this
down.
--
Stefan Haller
Ableton
http://www.ableton.com/
_______________________________________________
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