Poor dahdi_test results

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Sep 20, 2011 at 01:13:34PM -0700, Ryan Crowder wrote:
> # 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

Still strange. Although, since the overall result is 99.9x% range I
do not believe you will have any problems in this configuration.
Data is not being dropped, it is just that there is a delay when
it's being delivered to user space or the clock on your system is
jumping around slightly.

-- 
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



[Index of Archives]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite Backpacking]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]

  Powered by Linux