Performance tracker bug

[GoogleCodeExporter]

This is a tracker bug for performance related issues regarding:

 * Feature Extraction/Audio Analysis
 * Playlist Generation/Audio Analysis

Original issue reported on code.google.com by dominik....@gmail.com on 5 Nov 2008 at 5:42

[GoogleCodeExporter]

Current performance:

 * a song Scms model is computed in 1462ms
 * a playlist over 16000 tracks is computed in 2839ms

PC: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz, 8GB RAM

Possible speedups: Use multithreading for feature extraction: Issue #17

Original comment by dominik....@gmail.com on 5 Nov 2008 at 5:47

• Added labels: Performance

[GoogleCodeExporter]

Computing an scms model just got faster (revision 91), decoding now is the 
slowest
element in the feature extraction chain:

Mirage - mfcc Execution Time: 37ms
Mirage - scms created in: 18ms
Decoding/Downsampling/FFT: ~ 1 second (for MP3s)

PC: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz, 8GB RAM

Original comment by dominik....@gmail.com on 27 Feb 2009 at 2:55

[GoogleCodeExporter]

* playlist over 16000 tracks is now computed in 913ms (r94)

PC: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz, 8GB RAM

Original comment by dominik....@gmail.com on 5 Mar 2009 at 2:03

[GoogleCodeExporter]

Awesome !
Analysis and playlist generation both feel much faster.
I don't have numbers for before the changes, but here are my numbers with 
latest svn
and a library of about 2000 tracks:

Decoding : 1470ms
Mirage - mfcc Execution Time: 28ms
Mirage - scms created in: 13ms
Mirage - Total Execution Time: 1569ms

Mirage - playlist in: 207ms

PC: Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz, 1GB RAM.

Original comment by bertrand.lorentz@gmail.com on 5 Mar 2009 at 8:35