As my collection has grown, mp3tag takes much longer to load, export, import tags, doubling the number of files has meant a lot more than twice the time taken. There are likely causes for slowness:
- changing ID1 to ID2 tags, which requires a file rewrite if I change things, but I discount that as I know for sure all my files already have ID2 tags.
- disk speed and disk caching. I think I occasionally see this because sometimes mp3tag (and the disk system) seem to pause for a minute or so.
- windows memory handling. When I run Task Manager, I see mp3tag using 800 meg of memory. This is on a machine with only 1 Gig of memory, so windows is using virtual memory extensively. And I've seen Task Manager reporting approx 2 Gig page file use (my machine has max virtual memory 2.5 Gb). I have had an mp3tag message saying 'out of memory' when trying to export, followed by a program crash. I think this is the main cause of slowness when I try to load 50000 files or more!
mp3tag works very fast with 2000-10000 tracks loaded, works very slowly with 50000 tracks, and is almost guaranteed to stop working when 75000 tracks are loaded.
The answer is to load less files at any one time, but my question is how many? Can anyone (programming team?) explain mp3tag's memory use? Looks to me that it creates in-memory data structures when files are loaded or as tags are exported. I'm looking for a rule or thumb for how much memory is required for each task, per 1000 tracks? Then I can choose the number of files depending on which machine I'm on and how much memory is free, knowing in advance I'm unlikely to end up in difficulties.
Happy Christmas to all.