Slow scanning of music directories

[Ian Monroe]

On Sat, Dec 13, 2008 at 10:29 PM, Big O <illogical1 at gmail.com> wrote:
> For a while now I've been sitting on this bug, actually I started noticing
> it ever since we switched over to using mysql-embedded.
> I have a 25 Gb ~/Music directory in OS X (there is an additional 10 GB in
> /Volumes). The issue is scanning this ~/Music directory became painfully
> slow after switching to mysqle. It seems as if it was even slower than with
> sqlite.
> I just moved a directory and the update collection scan took at least five
> minutes to update that 25 GB collection. I say at least five minutes because
> I only noticed after the fan on my laptop got noisy because Amarok's CPU
> usage was > 100% (amarokcollectionscanner itself was using around 16%
> consistently).
> This means it took > five minutes (7-8 perhaps) to update a collection
> whenever new music lands in the watch path. This is, all kinds of
> unacceptable, primarily because of the CPU usage involved; also because this
> isn't even all of my music yet. Does anyone have any idea of what's going on
> and whether or not this is "normal".

7-8 minutes to do a total rescan of 25 gigs is quite fast. Which is
probably what is happening.

So the problem is that incremental scanning isn't working correctly likely.

What directory is having a file added to it? Is it a top-level directory?

Ian