Subject: [ecasound] more profiling information
From: Kai Vehmanen (k_AT_eca.cx)
Date: Mon Oct 15 2001 - 03:59:11 EEST
I've now added more profiling code, this time to the engine itself.
Here's a sample output from playing a 15sec 10ch/32bit wav file
to 0.9 ALSA device, under a minor load:
--cut--
(eca-engine) *** profile begin ***
Total loops: 2584
Loops faster than realtime: 1260 (<23.2 msec)
Loops slower than realtime: 1324 (>=23.2 msec)
Loops slower than realtime: 9 (>46.4 msec)
Loops exceeding all buffering: 0 (>185.8 msec)
Fastest loop: 1.2 msec.
Slowest loop: 108.3 msec.
Average loop time: 23.1 msec.
(eca-engine) *** profile end ***
(audioio-proxy-server) *** profile begin ***
profile_full_rep: 2
profile_no_processing_rep: 54
profile_not_full_anymore_rep: 2434
profile_processing_rep: 246
profile_read_xrun_danger_rep: 1344
profile_write_xrun_danger_rep: 0
profile_rounds_total_rep: 2736
(audioio-proxy-server) *** profile end ***
--cut---
The slowest loop (108.3msec) is still far from the critical limit of
185.8ms. On the other hand the amount of dangerous loops (9 times over
46.4msec) looks bad. The disk i/o subsystem had a quite a few difficult
spots (1344 xrun_danger events), but has still survived the load (based on
engine profile output).
This information is enabled by default on all 2.1.x versions, and is
printed after any app using libecasound exits (ecasound, ecaplay, ecawave,
python apps, etc).
If you have any performance problems, send the above profile info to me
(or to this list if it's really interesting :)), so we can try to figure
out what is causing problems.
-- http://www.eca.cx Audio software for Linux!-- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request_AT_wakkanet.fi>.
This archive was generated by hypermail 2b28 : Mon Oct 15 2001 - 03:56:10 EEST