Andrew Kohlsmith wrote:
On Saturday 05 November 2005 02:54, Tzafrir Cohen wrote:
Asterisk here falls under "desktop": Much like interactive desktop apps
it need timely response rather than more time at the CPU.
I am not so sure; asterisk is a multithreaded app, yes, but I would think that
kernel preemption would be a far bigger 'win' with Asterisk than a far more
granular (but heavier processor use as a result) timer.
I have not done any real benchmarks to prove or disprove this, but more of a
Greek science method. :-)
-A.
I realize I'm responding to this way late, but I was following the
discussion on the linux kernel list when they were debating the change
of the default from 1000Hz to 250Hz. The biggest outcry against the
change were from a lot of the multimedia people, who complained that a
lot of sound and multimedia stuff, midi, etc., would suffer greatly from
a slower tickrate. I'd imagine a lot of the codecs that asterisk uses
would have the same issue.
Stephen
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
