View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004655 | MMW v4 | DB/FileMonitor | public | 2008-05-08 20:58 | 2008-05-09 03:32 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.0 | ||||
| Summary | 0004655: Performance: Memory is used at a rate of 1K per track that appears in a view triggering slowdowns | ||||
| Description | I was just doing some testing on a large DB and noticed that: -for each track in a DB memory utilization grows by ~1KB when the track appears in a view. e.g. if there are 500,000 tracks in the DB and user clicks the Artist node --> Memory utilization by MediaMonkey grows to 550,000 KB -As a consequence of the above, performance of MediaMonkey slows dramatically as available memory is used up. For instance, when I click the Artist node, the first 400,000 tracks are read in 0000025:0000030 seconds, but the next 150,000 tracks take > 5 minutes to be read. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
That's currently as designed. Track that's in a view must occupy some memory, we can further improve it for future versions, but we already made some improvements in this area. Note that the DB approach MM uses has an advantage over other apps in case you don't need to view all your tracks at once - then even though you work with _huge_ collection, MM is still very fast and needs just a little memory. |
