# chrt -f 99 dahdi_test -v -c 5 Opened pseudo dahdi interface, measuring accuracy... 8192 samples in 8159.824 system clock sample intervals (99.607%) 8192 samples in 8239.544 system clock sample intervals (100.580%) 8192 samples in 8159.856 system clock sample intervals (99.608%) 8192 samples in 8159.833 system clock sample intervals (99.607%) 8192 samples in 8239.856 system clock sample intervals (100.584%) --- Results after 5 passes --- Best: 99.608 -- Worst: 99.416 -- Average: 99.531525, Difference: 99.997346 Thanks for the help! -----Original Message----- From: asterisk-ss7-bounces@xxxxxxxxxxxxxxxx [mailto:asterisk-ss7-bounces at lists.digium.com] On Behalf Of Shaun Ruffell Sent: Tuesday, September 20, 2011 12:31 PM To: asterisk-ss7 at lists.digium.com Subject: Re: Poor dahdi_test results On Tue, Sep 20, 2011 at 11:38:35AM -0700, Ryan Crowder wrote: > Do you think this error has anything to do with it? > > dahdi_genconf > /usr/sbin/dahdi_genconf: missing default group (termtype=UNKNOWN) > It doesn't populate dahdi-channels.conf so I have to configure > chan_dahdi.conf manually. You can safely ignore this. There is an open issue [1] for this is the DAHDI-Tools project on the issue tracker. [1] https://issues.asterisk.org/jira/browse/DAHTOOL-55 > Here are the results... not really better. > :/etc/dahdi# dahdi_test > Opened pseudo dahdi interface, measuring accuracy... > 99.608% 99.419% 99.608% 99.608% 99.415% 99.608% 99.415% 99.608% > 99.608% 99.416% 99.608% 99.415% 99.608% 99.608% 99.415% 99.608% > 99.415% 99.608% 99.608% 99.416% 99.608% 99.415% 99.608% 99.608% > 99.415% 99.608% 99.415% 99.608% 99.608% 99.415% 99.608% 99.415% ^C > --- Results after 32 passes --- > Best: 99.608 -- Worst: 99.415 -- Average: 99.529880, Difference: > 100.004770 > :/etc/dahdi# dahdi_test -v -c 5 > Opened pseudo dahdi interface, measuring accuracy... > > 8192 samples in 8159.801 system clock sample intervals (99.607%) > 8192 samples in 8159.528 system clock sample intervals (99.604%) > 8192 samples in 8239.840 system clock sample intervals (100.584%) > 8192 samples in 8159.856 system clock sample intervals (99.608%) > 8192 samples in 8239.840 system clock sample intervals (100.584%) > --- Results after 5 passes --- > Best: 99.608 -- Worst: 99.416 -- Average: 99.530042, Difference: > 99.997230 Interesting. This looks fine then and it's most likely a result of the dahdi_test process not being scheduled on your system in a timely fashion. Your cummulative timing results were 99.997% which is good. What do you get when you run: $ chrt -f 99 dahdi_test -v -c 5 That will run the dahdi_test process at the highest possible priority. -- Shaun Ruffell Digium, Inc. | Linux Kernel Developer 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 -- asterisk-ss7 mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-ss7 CONFIDENTIALITY / PRIVILEGE NOTICE: This transmission and any attachments are intended solely for the addressee. This transmission is covered by the Electronic Communications Privacy Act, 18 U.S.C ?? 2510-2521. The information contained in this transmission is confidential in nature and protected from further use or disclosure under U.S. Pub. L. 106-102, 113 U.S. Stat. 1338 (1999), and may be subject to attorney-client or other legal privilege. Your use or disclosure of this information for any purpose other than that intended by its transmittal is strictly prohibited, and may subject you to fines and/or penalties under federal and state law. If you are not the intended recipient of this transmission, please DESTROY ALL COPIES RECEIVED and confirm destruction to the sender via return transmittal.
|