Version: (using KDE 4.1.2) Compiler: gcc 4.3.2 -march=native -O2 -pipe OS: Linux Installed from: Compiled From Sources Compiled amarok 1.94 from source with gcc 4.3.2 I wanted to clean up a little of my disk space, and get my music collection in a little better shape. Admittedly, the collection is a little large, with about 16,000 songs. To reproduce: Right-Click on my local collection, and then pick Organize files. Ticked Sort by file type, and Replace spaces with underscores, restrict to ASCII. Then clicked on continue. The amarok gui becomes completely unusable, and when switching between screens and back it does not redraw. So I leave it alone for a few hours, even though file renames and moving on the same filesystem should be fairly quick. Result: When I returned to my machine, all of my 2GB of ram was claimed by amarok, the CPU was still at 100% and my SWAP was thrashing madly. While amarok did not actually crash, it did become completely unresponsive. Investigation: So, I killed the amarok process. Then I try again with a smaller set of files, ( one band ) and the file move operation was done almost instantly. So I try ever bigger selections of files with the time used by amarok to sort and move them increasing linearly with the amount of files picked. At about ten bands or so selected I run out of ram again and the time waited increases exponentially as swap is terribly slow. Conclusion: Seems to me that amarok is trying to load every song in my collection in to ram before starting to move them. This is fine for handling small amounts of data, but makes no sense when pointed at a collection of about 100GB. Expected behaviour: amarok should be able to deal with huge amounts of files gracefully. Check how much ram is available and only run batches that will actually fit in to the RAM in serial rather than try to move all the files at once.
Sounds like a reasonable request.
Targeting this for 2.0.1 as it's a pretty important feature (and many people are going to want to organize their entire collection, so it will probably effect the masses.)
Is this still valid with SVN trunk? The report is super old...
Yes, this report is still valid.
Any news on this? Changed version.
Amarok does not eat up huge amounts of memory anymore. Collection management still leaves a little to be desired, though. I suppose that will have to go into usability bugs? I was able to move around 20Gb worth of songs from a directory to my collection.