Squeezecenter startup is very slow, log points to TrackStat actions

[GoogleCodeExporter]

Which plugin is the bug/enhancement related to ?
-Trackstat

What version of SlimServer/SqueezeCeneter are you using? On what operating 
system?
-Squeezecenter 7.3.1 rev 24298 
-Windows XP (SP 3)

Could you describe the problem or enhancment?
-When I start Squeezecenter, it takes several minutes to become responsive.  
The log file indicates that the slow steps are all TrackStat-related 
actions.

What steps will reproduce the problem?
1. Start Squeezecenter

The first really time-consuming action starts at [08-12-15 15:11:35.0005] 
in the attached log file snippet.

In particular:

[08-12-15 15:12:33.8438] Plugins::TrackStat::Storage::refreshTracks (1175) 
Finished updating musicbrainz id's in statistic data based on urls, updated 
0 items : It took 58.843465 seconds

[08-12-15 15:17:36.1876] Plugins::TrackStat::Storage::refreshTracks (1200) 
Finished updating ratings in standard slimserver database based on urls, 
updated 0 items : It took 302.343492 seconds

[08-12-15 15:23:25.0782] Plugins::TrackStat::Storage::refreshTracks (1225) 
Finished updating added times in statistic data based on urls, updated 0 
items : It took 348.890364 seconds

[08-12-15 15:28:08.3282] Plugins::TrackStat::Storage::refreshTracks (1312) 
Finished adding tracks without added times in statistic data based on urls, 
added 12 items : It took 261.843319 seconds

This occurs every time I restart Squeezecenter.

Thank you for your help!

Original issue reported on code.google.com by jordache on 15 Dec 2008 at 9:36

Attachments:

• server.log

[GoogleCodeExporter]

Your times seems to be a bit long, I suppose your library is pretty large ?

There is an option in the TrackStat settings where you can disable the refresh
operation at startup, if you disable this you will still be fine as long as you 
don't
move or rename any files.

Original comment by erlan...@hotmail.com on 16 Dec 2008 at 6:14

• Changed state: Accepted
• Added labels: Plugin-TrackStat, Priority-Medium, Type-Enhancement

[GoogleCodeExporter]

Erland,

Thanks for the reply.  Yes, my library is currently 65,702 songs.  The problem 
with
disabling the refresh is that I frequently add/change files and move things 
around as
I try to keep it organized.  Is there any way to move the refresh into a 
nightly job
or something like that, as opposed to on startup?

Thanks,
Jordan

Original comment by jordache on 16 Dec 2008 at 1:47

[GoogleCodeExporter]

Just saw that I can have it do a refresh after a rescan instead of on startup.  
Since 
I'm doing a nightly rescan anyway, I think that should be fine.  I'd still like 
to 
keep this open as an enhancement request though, as those times still seem 
quite 
long.  Thank you.

Original comment by jordache on 16 Dec 2008 at 2:00

[GoogleCodeExporter]

I have the same problem with a library of 61156 songs. I'm using Squeezeserver 
7.70 (I downgraded to see if that would affect the refresh time) on Debian 
Linux (Version 7.6). The refresh of Trackstat is ridiculously long both at 
startup and on rescan. It's so long that on an overnight scan I can't reliably 
use my Squeezebox Boom as an alarm clock, because the server may be down too 
long.  Getting better speed on Trackstat refresh should be something kept on 
the list of issues.

Original comment by favolasc...@gmail.com on 14 Oct 2014 at 2:17