> My, i admit rather short test reveals, that the trackscan scan task went
I guess that should read "trackstat"?
> don't from 3 hours to 4 min on LMS restart and from 3 hours to 15 min on
> forced rescan. Even though modifying the SELECT statement to prevent
> musicbrainz_id duplicates will bring the scanning down to 4 secs each,
> so......
Well, that's a good result :-). Would be interesting to know which tweak
makes the difference, or whether it's really the combination of them all.
> Another improvement is in the webinterface everywhere where cover images
> needs to be displayed it "seems" faster.....
Ok, I'll see what I can learn from that plugin. Thanks for the data point!
I guess that should read "trackstat"?
> don't from 3 hours to 4 min on LMS restart and from 3 hours to 15 min on
> forced rescan. Even though modifying the SELECT statement to prevent
> musicbrainz_id duplicates will bring the scanning down to 4 secs each,
> so......
Well, that's a good result :-). Would be interesting to know which tweak
makes the difference, or whether it's really the combination of them all.
> Another improvement is in the webinterface everywhere where cover images
> needs to be displayed it "seems" faster.....
Ok, I'll see what I can learn from that plugin. Thanks for the data point!