Mediascanner scope "doesn't behave well" with lots of music (~30GB)

[Pete Woods]

- via Rick... Music scope with lots (~30gb) of music/content doesn't behave well, i.e. lags, empty art, etc

[James Henstridge (jamesh)]

We'll need a bit more information to determine the cause here.

Given that we're talking about 30GB of music, presumably it's on an SD card? This would give limited IO bandwidth, but the index itself used by the scope would still be on faster internal storage.

My guess is that the slowness is on the shell side and probably related to rendering the album art. If the music has embedded album art, we will be hitting the SD card to extract it on display which could be an IO bottleneck. If the music does not have embedded art, the online art fetcher would be in use, and we might be issuing too many concurrent requests.

[Michi Henning (michihenning)]

I'm closing this because it's very old.

What matters here is not so much the the number of gigabytes, but the number of songs. I've stress-tested with thousands of (very short) songs. (To the thumbnailer and mediascanner, the size of the song is essentially irrelevant; the cost of extracting ID3 tags from a large song is essentially the same as from a small one.)

The thumbnailer, music-app, and music-scope all cope well with very large collections now.

[Michi Henning (michihenning)]

Pete, Rick, if you still see a problem, please re-open.