Version: 1.4.4 (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux System Info: I have about 9,000 ogg and mp3 files. 8,700+ in one directory and about 600 in another. I'm using postgres to store my collection. What Happens: If I make changes (say by moving a directory around in my collection), then the next automatic update (or if I use re-scan) it scans my collection. When it gets to about 99% or so (the end, basically) Amarok then becomes non-responsive. If you move it off screen, it doesn't redraw the screen, etc. If I look at top at that time, I see that postmaster is using some CPU, so I assume that it's writing to the database at that time. What I Expect: I click re-scan (or an auto update happens) and I should notice *no* impact on using Amarok or the system. Suggestions: If the problem is indeed that the main Amarok thread (or at least the UI thread) is hanging waiting for postgres to finish a transaction at the end, then: * Make sure transactions are small. Say, per file. * Do the transactions as you go through the files, not at the end. * Don't hang the UI on transactions. Service other things and come back to see what the database said at the end. Updating a collection isn't a real-time activity. :-) Ciao!
Second that request. I just started an update-scan near the end of an track, so after it ended amarok was quiet until the sql stuff was done ~ 20-30 sec. (it was only a small update). Nothing to worry about but certainly not nice :)
Amarok no longer uses Postgresql.