Comment 2 for bug 624220

Hi, sorry I missed this bug so far: obscured by too much work related launchpad mail ;). This has been one of the things that have proven hard to solve, because autoqueue potentially has a lot of work to do, especially when analyzing new tracks with mirage, or when looking up connections on last.fm: it has to write data to sqlite, and wait for that to complete to be able to query.

I've made a few changes in trunk that seem very promising however: I've moved all database writes and analysis to a separate process that's started by autoqueue when firing up quodlibet. This means all of the heavy lifting happens outside of the plugin, and it's had a huge effect on the responsiveness in my case (~170K tracks).

I'll try and release this when it stabilizes, but I've been using it for a month or two now, and it seems to have no discernable downsides yet.

Let me know if this solves you guys' problems!