Bartek Kania wrote:
> Those are great results!
> I don't know how xen handles scheduling but I'm always careful with
> anything that might add latency to the scheduling or timing. 1ms
> resolution is the minimum needed (a little less can be accepted since
> jitterbuffers can usually handle that).
Xen has a realtime scheduler called SEDF, which I was using. It's
slightly over my head, and I'm not sure I'm doing everything right yet.
But I'm essentially running Linux inside a realtime scheduler. It would
seem however, that Xen is capable of dealing with the timers OpenPBX is
using, because I ran Asterisk with the same configuration, and the
results were unacceptable.
I used scheduling parameters that according to the Xen documentation
tell it to make that Linux instance have a 5ms slice every 20ms. (In
fact, I used an example out of the documentation.) We use RTP with ulaw
20ms packets. Does OpenPBX actually need to wakeup every 1ms, or does it
need to wakeup every 20ms with better than 1ms resolution?
> Did you use the -p option to opbx (it makes it run with higher priority)?
Yes. Unfortunately, building XenLinux kernels disables CONFIG_PREEMPT,
or I'd have turned that on too.
---Nathan
_______________________________________________
Openpbx-users mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-users
