Woof! On Fri, 14 May 2010 16:06:14 -0400, Michael Jerris <[email protected]> wrote:
> 1000 is what it should be set to. What he said! At 1000 Hz, that's 1 tick per mS, and allows 10, 20, 30 mS RTP timers with +/- 1 mS jitter. Good enough to not require real-time or any other special processing. At 100 Hz, that's 1 tick per 10 mS and with a +/- 10 mS jitter, you can see that that would cause, um, *issues* with trying to generate a 10 or even 20 mS RTP stream. At 256 Hz, it's really bad, because it doesn't divide into 10 mS very well at all! The whole idea with 'tickless' was to pacify the laptop users who were SURE that all those ticks were killing their battery life. Last I looked into it (some years ago), there was no PROOF of this, just lots of flames. Then, if I recall correctly, Linus tried to end the wars by declaring "256" as the new default value, as it should pacify the server guys and the laptop guys. Alas, it really screwed up the VoIP guys! But Red Hat (dog bless them) has kept 1000 Hz, and CentOS picks that up, which is one of the reasons both sipXecs and FreeSWITCH recommend CentOS as the distro of choice. And there has been some chatter about idle FS consuming CPU, and it may even be a real issue, but I know Anthony dismisses it as a non-problem, and thus so should we. --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
