[asterisk-users] Core show translation 4000ms
Hi list, we have 2 asterisk boxes in VM (kvm) on 2 different Dell servers, one is Lenny kernel 2.6.26 asterisk 1.6.2.20, the second CentOS 2.6.18 asterisk 1.4.36 (Elastix). Both 64bits, no hardware involved, dahdi on both machines for meetme timing. Doing core show translation give on the Lenny server Translation times between formats (in microseconds) for one second of data Source Format (Rows) Destination Format (Columns) g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 siren7 siren14 slin16 g723 - - - -- - - - - - - - - - - - gsm - - 2 2 4001 2 1 2 - - - 4001 4002 - - 4003 ulaw - 4001 - 1 4001 2 1 2 - - - 4001 4002 - - 4003 alaw - 4001 1 - 4001 2 1 2 - - - 4001 4002 - - 4003 [...] and on the CentOS one g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 g723- ---- -- -- - --- gsm- -222 21 3- 6 -22 ulaw- 2-12 21 3- 6 -22 alaw- 21-2 21 3- 6 -22 [...] Why do we have such latency on the Lenny machine for the codec translation? Is this due to a kernel parameter? Thanks for any hint -- Daniel -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Core show translation 4000ms
On 09/30/2011 03:56 AM, Administrator TOOTAI wrote: Hi list, we have 2 asterisk boxes in VM (kvm) on 2 different Dell servers, one is Lenny kernel 2.6.26 asterisk 1.6.2.20, the second CentOS 2.6.18 asterisk 1.4.36 (Elastix). Both 64bits, no hardware involved, dahdi on both machines for meetme timing. Doing core show translation give on the Lenny server Translation times between formats (in microseconds) for one second of data Source Format (Rows) Destination Format (Columns) g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 siren7 siren14 slin16 g723 - - - - - - - - - - - - - - - - gsm - - 2 2 4001 2 1 2 - - - 4001 4002 - - 4003 ulaw - 4001 - 1 4001 2 1 2 - - - 4001 4002 - - 4003 alaw - 4001 1 - 4001 2 1 2 - - - 4001 4002 - - 4003 [...] and on the CentOS one g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 g723 - - - - - - - - - - - - - gsm - - 2 2 2 2 1 3 - 6 - 2 2 ulaw - 2 - 1 2 2 1 3 - 6 - 2 2 alaw - 2 1 - 2 2 1 3 - 6 - 2 2 [...] Why do we have such latency on the Lenny machine for the codec translation? Is this due to a kernel parameter? Because you didn't read the output. It clearly says (in microseconds) in the 1.6.x output. -- Kevin P. Fleming Digium, Inc. | Director of Software Technologies Jabber: kflem...@digium.com | SIP: kpflem...@digium.com | Skype: kpfleming 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at www.digium.com www.asterisk.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Core show translation 4000ms
Le 30/09/2011 14:05, Kevin P. Fleming a écrit : On 09/30/2011 03:56 AM, Administrator TOOTAI wrote: Hi list, we have 2 asterisk boxes in VM (kvm) on 2 different Dell servers, one is Lenny kernel 2.6.26 asterisk 1.6.2.20, the second CentOS 2.6.18 asterisk 1.4.36 (Elastix). Both 64bits, no hardware involved, dahdi on both machines for meetme timing. Doing core show translation give on the Lenny server Translation times between formats (in microseconds) for one second of data Source Format (Rows) Destination Format (Columns) g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 siren7 siren14 slin16 g723 - - - - - - - - - - - - - - - - gsm - - 2 2 4001 2 1 2 - - - 4001 4002 - - 4003 ulaw - 4001 - 1 4001 2 1 2 - - - 4001 4002 - - 4003 alaw - 4001 1 - 4001 2 1 2 - - - 4001 4002 - - 4003 [...] and on the CentOS one g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 g723 - - - - - - - - - - - - - gsm - - 2 2 2 2 1 3 - 6 - 2 2 ulaw - 2 - 1 2 2 1 3 - 6 - 2 2 alaw - 2 1 - 2 2 1 3 - 6 - 2 2 [...] Why do we have such latency on the Lenny machine for the codec translation? Is this due to a kernel parameter? Because you didn't read the output. It clearly says (in microseconds) in the 1.6.x output. Well, I surely ask the wrong way, sorry: ms or us, 4001 from ulaw to gsm and 2 the other way, still a huge difference. The output from centos shows similar value in both directions. -- Daniel -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Core show translation 4000ms
On 09/30/2011 07:49 AM, Administrator TOOTAI wrote: Le 30/09/2011 14:05, Kevin P. Fleming a écrit : On 09/30/2011 03:56 AM, Administrator TOOTAI wrote: Hi list, we have 2 asterisk boxes in VM (kvm) on 2 different Dell servers, one is Lenny kernel 2.6.26 asterisk 1.6.2.20, the second CentOS 2.6.18 asterisk 1.4.36 (Elastix). Both 64bits, no hardware involved, dahdi on both machines for meetme timing. Doing core show translation give on the Lenny server Translation times between formats (in microseconds) for one second of data Source Format (Rows) Destination Format (Columns) g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 siren7 siren14 slin16 g723 - - - - - - - - - - - - - - - - gsm - - 2 2 4001 2 1 2 - - - 4001 4002 - - 4003 ulaw - 4001 - 1 4001 2 1 2 - - - 4001 4002 - - 4003 alaw - 4001 1 - 4001 2 1 2 - - - 4001 4002 - - 4003 [...] and on the CentOS one g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 g723 - - - - - - - - - - - - - gsm - - 2 2 2 2 1 3 - 6 - 2 2 ulaw - 2 - 1 2 2 1 3 - 6 - 2 2 alaw - 2 1 - 2 2 1 3 - 6 - 2 2 [...] Why do we have such latency on the Lenny machine for the codec translation? Is this due to a kernel parameter? Because you didn't read the output. It clearly says (in microseconds) in the 1.6.x output. Well, I surely ask the wrong way, sorry: ms or us, 4001 from ulaw to gsm and 2 the other way, still a huge difference. The output from centos shows similar value in both directions. This is why the output was changed to microseconds from milliseconds; in the older version, the lowest number that should be shown was 1 millisecond, even if the actual amount of time consumed was 10 microseconds (or less). The 1 numbers in the output from the older could easily have been 0.02, which would be closer to the output from the new version. -- Kevin P. Fleming Digium, Inc. | Director of Software Technologies Jabber: kflem...@digium.com | SIP: kpflem...@digium.com | Skype: kpfleming 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at www.digium.com www.asterisk.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Core show translation 4000ms
In article 4e85d19f.4090...@digium.com, Kevin P. Fleming kpflem...@digium.com wrote: On 09/30/2011 07:49 AM, Administrator TOOTAI wrote: Le 30/09/2011 14:05, Kevin P. Fleming a écrit : On 09/30/2011 03:56 AM, Administrator TOOTAI wrote: Hi list, we have 2 asterisk boxes in VM (kvm) on 2 different Dell servers, one is Lenny kernel 2.6.26 asterisk 1.6.2.20, the second CentOS 2.6.18 asterisk 1.4.36 (Elastix). Both 64bits, no hardware involved, dahdi on both machines for meetme timing. Doing core show translation give on the Lenny server Translation times between formats (in microseconds) for one second of data Source Format (Rows) Destination Format (Columns) g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 siren7 siren14 slin16 g723 - - - - - - - - - - - - - - - - gsm - - 2 2 4001 2 1 2 - - - 4001 4002 - - 4003 ulaw - 4001 - 1 4001 2 1 2 - - - 4001 4002 - - 4003 alaw - 4001 1 - 4001 2 1 2 - - - 4001 4002 - - 4003 [...] and on the CentOS one g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 g723 - - - - - - - - - - - - - gsm - - 2 2 2 2 1 3 - 6 - 2 2 ulaw - 2 - 1 2 2 1 3 - 6 - 2 2 alaw - 2 1 - 2 2 1 3 - 6 - 2 2 [...] Why do we have such latency on the Lenny machine for the codec translation? Is this due to a kernel parameter? Because you didn't read the output. It clearly says (in microseconds) in the 1.6.x output. Well, I surely ask the wrong way, sorry: ms or us, 4001 from ulaw to gsm and 2 the other way, still a huge difference. The output from centos shows similar value in both directions. This is why the output was changed to microseconds from milliseconds; in the older version, the lowest number that should be shown was 1 millisecond, even if the actual amount of time consumed was 10 microseconds (or less). The 1 numbers in the output from the older could easily have been 0.02, which would be closer to the output from the new version. Maybe, but that still doesn't explain why there is a factor of 2000 between some conversions and others. And 4001, 4002 and 4003 are remarkably like a big round number plus a tiny offset! I would agree with the OP that the values shown look suspicious and would bear some investigating... Cheers Tony -- Tony Mountifield Work: t...@softins.co.uk - http://www.softins.co.uk Play: t...@mountifield.org - http://tony.mountifield.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Core show translation 4000ms
I always use the recalc option to show translations, it seems to provide much more accurate numbers. Example: core show translation recalc 20 -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Tony Mountifield Sent: Friday, September 30, 2011 10:54 AM To: asterisk-users@lists.digium.com Subject: Re: [asterisk-users] Core show translation 4000ms Maybe, but that still doesn't explain why there is a factor of 2000 between some conversions and others. And 4001, 4002 and 4003 are remarkably like a big round number plus a tiny offset! I would agree with the OP that the values shown look suspicious and would bear some investigating... -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Core show translation 4000ms
On 09/30/2011 09:53 AM, Tony Mountifield wrote: In article 4e85d19f.4090...@digium.com, Kevin P. Fleming kpflem...@digium.com wrote: This is why the output was changed to microseconds from milliseconds; in the older version, the lowest number that should be shown was 1 millisecond, even if the actual amount of time consumed was 10 microseconds (or less). The 1 numbers in the output from the older could easily have been 0.02, which would be closer to the output from the new version. Maybe, but that still doesn't explain why there is a factor of 2000 between some conversions and others. And 4001, 4002 and 4003 are remarkably like a big round number plus a tiny offset! I would agree with the OP that the values shown look suspicious and would bear some investigating... I believe the way it gets calculated was also changed a bit. You'll commonly see numbers that are near multiples of 1000. If I'm not mistaken these are the duration of a context switch (or several context switches), which means that with this output, you can guess that his kernel is probably compiled with CONFIG_HZ_250. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Core show translation 4000ms
Le 30/09/2011 16:59, Eric Wieling a écrit : I always use the recalc option to show translations, it seems to provide much more accurate numbers. Example: core show translation recalc 20 Lenny kernel, new values, still 1000 microseconds between both directions Translation times between formats (in microseconds) for one second of data Source Format (Rows) Destination Format (Columns) g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 siren7 siren14 slin16 g723 - - - -- - - - - - - - - - - - gsm - - 601 601 3800 800 600 2000 - - - 3800 1200 - - 2000 ulaw - 1601 - 1 3201 201 1 1401 - - - 3201 601 - - 1401 alaw - 1601 1 - 3201 201 1 1401 - - - 3201 601 - - 1401 CentOS, no changes g723 gsm ulaw alaw g726aal2 adpcm slin lpc10 g729 speex ilbc g726 g722 g723- ---- -- -- - --- gsm- -222 21 5- 7 -22 ulaw- 2-12 21 5- 7 -22 alaw- 21-2 21 5- 7 -22 I ran the same command on an Squeeze 2.6.32 kernel running 1.8.7 asterisk: values are neer those from CentOS asterisk 1.4 version -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Tony Mountifield Sent: Friday, September 30, 2011 10:54 AM To: asterisk-users@lists.digium.com Subject: Re: [asterisk-users] Core show translation 4000ms Maybe, but that still doesn't explain why there is a factor of 2000 between some conversions and others. And 4001, 4002 and 4003 are remarkably like a big round number plus a tiny offset! I would agree with the OP that the values shown look suspicious and would bear some investigating... [...] -- Daniel -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Core show translation 4000ms
Le 30/09/2011 17:02, Jason Parker a écrit : On 09/30/2011 09:53 AM, Tony Mountifield wrote: In article4e85d19f.4090...@digium.com, Kevin P. Flemingkpflem...@digium.com wrote: This is why the output was changed to microseconds from milliseconds; in the older version, the lowest number that should be shown was 1 millisecond, even if the actual amount of time consumed was 10 microseconds (or less). The 1 numbers in the output from the older could easily have been 0.02, which would be closer to the output from the new version. Maybe, but that still doesn't explain why there is a factor of 2000 between some conversions and others. And 4001, 4002 and 4003 are remarkably like a big round number plus a tiny offset! I would agree with the OP that the values shown look suspicious and would bear some investigating... I believe the way it gets calculated was also changed a bit. You'll commonly see numbers that are near multiples of 1000. If I'm not mistaken these are the duration of a context switch (or several context switches), which means that with this output, you can guess that his kernel is probably compiled with CONFIG_HZ_250. As Tony pointed out, it's the factor between both translation directions which push me to ask. I can leave with microseconds and understand the why, but values should not have a so big interval. -- Daniel -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
