Re: Socket recv behaviour in real-time context
Re: Socket recv behaviour in real-time context
- Subject: Re: Socket recv behaviour in real-time context
- From: Jeff Moore <email@hidden>
- Date: Mon, 16 Mar 2009 11:26:31 -0700
On Mar 16, 2009, at 10:23 AM, Stéphane Letz wrote:
Well the RT thread is not disturbed by other RT threads! The high
latencies I can see occurs already when a *compilation* is done. I
could record several latencies peaks (like 9,2 ms or 18.4 ms) using
Shark with an audio network process that runs at 256 frames / 44.1
(so a period that should be about 5 ms.) The system call that has
the long wait time is "recvfrom_nocancel" and is interleaved with
system calls related to the compilation.
Hmm. It sounds like you have some part of your your work being done by
either one thread with a large work queue or just a plain low priority
thread. It could also be that there are occasional blocks in the
system calls. You'd need to do a little more digging into the problem.
Since there are latency peaks, you might want to also do a time
profile trace to see if you can see what was going on during those
latency peaks.
But I don't see how to get a trace of what happens in the kernel at
that time... Should the /Developer/Examples/CoreAudio/PublicUtility/
CALatencyLog.cpp tools be used then ?
That would certainly work. You can also directly use the command line
tracing tools.
--
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