using 2.6.10-rc3-mm with Ingo's latest Real-Time Preempt on a pentium
M 1.6ghz laptop with a gig of ram. The test was done as a normal user
using the realtime-lsm patch and I have Rui's rtirq script up and
running. One of the three tests was completed while compiling gnuplot
in the background :).
*********** CONSOLIDATED RESULTS ************
Total seconds ran . . . . . . : 1200
Number of clients . . . . . . : 20
Ports per client . . . . . . : 4
Frames per buffer . . . . . . : 64
*********************************************
Summary Result Count . . . . : 3 / 3
*********************************************
Timeout Rate . . . . . . . . :( 0.0)/hour
XRUN Rate . . . . . . . . . . : 4.0 /hour
Delay Rate (>spare time) . . : 85477.0 /hour
Delay Rate (>1000 usecs) . . : 0.0 /hour
Delay Maximum . . . . . . . . : 0 usecs
Cycle Maximum . . . . . . . . : 0 usecs
Average DSP Load. . . . . . . : 34.0 %
Average CPU System Load . . . : 25.5 %
Average CPU User Load . . . . : 27.7 %
Average CPU Nice Load . . . . : 0.0 %
Average CPU I/O Wait Load . . : 0.1 %
Average CPU IRQ Load . . . . : 0.0 %
Average CPU Soft-IRQ Load . . : 0.0 %
Average Interrupt Rate . . . : 1881.0 /sec
Average Context-Switch Rate . : 42065.8 /sec
*********************************************
I ran it 3 times. twice at 300s and once for 600 seconds. However I
dont think It actually ran for 5 minutes or 10 minutes. Every time I
ran it I got a similar warning/error (maybe I am supposed to get
this?)
$ ./jack_test3_run.sh 600
Launching jack_test3_nmeter...done.
Launching 20 ./jack_test3_client(s) instance(s)...done.
Running jackd...1...2...3...4...5...6...7...8...9...10...11...12...13...14...15...16..../jack_test3_run.sh:
line 48: 32325 Killed ${CMD} >>${LOG} 2>&1
done.
./jack_test3_run.sh: line 48: 1007 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 1389 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 1784 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 2262 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 2419 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 2598 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 2901 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 3226 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 3834 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 4257 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 4348 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 4381 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 4666 Broken pipe ${CMD} >>${LOG} 2>&1
./jack_test3_run.sh: line 48: 5115 Broken pipe ${CMD} >>${LOG} 2>&1
Killing jack_test3_nmeter..../jack_test3_run.sh: line 144: 31774
Terminated ( ${NMETER} ${NMETER_ARGS} >>${LOG} 2>&1 )
OK.
17...************* SUMMARY RESULT ****************
Total seconds ran . . . . . . : 600
Number of clients . . . . . . : 20
Ports per client . . . . . . : 4
Frames per buffer . . . . . . : 64
*********************************************
Timeout Count . . . . . . . . :( 0)
XRUN Count . . . . . . . . . : 2
Delay Count (>spare time) . . : 29224
Delay Count (>1000 usecs) . . : 0
Delay Maximum . . . . . . . . : 0 usecs
Cycle Maximum . . . . . . . . : 0 usecs
Average DSP Load. . . . . . . : 36.7 %
Average CPU System Load . . . : 38.8 %
Average CPU User Load . . . . : 61.0 %
Average CPU Nice Load . . . . : 0.0 %
Average CPU I/O Wait Load . . : 0.2 %
Average CPU IRQ Load . . . . : 0.0 %
Average CPU Soft-IRQ Load . . : 0.0 %
Average Interrupt Rate . . . : 1857.8 /sec
Average Context-Switch Rate . : 43960.2 /sec
*********************************************
Also my context-switch rate is WAY higher than other folks. Am I
missing a tuning step?
over all I have been super happy with the latest ingo patch.
m.
On Thu, 30 Dec 2004 11:19:14 -0000 (WET), Rui Nuno Capela
<rncbc@xxxxxxxxx> wrote:
> Hi,
>
> As posted before on LKML, here goes my contained jackd test-suite (see
> attached tarball, jackd_test3.2.tar.gz).
>
