Refreshing object in dashboard- hourglass for longer than expected

[ginjaninja 533]

Version 3.0.5306.42925 (although not a new phenomenon)

 

 

Sometimes when refreshing an object in dashboard, the hourglass persists for a very long time (much longer than would be anticipated given the work the fetchers have to do.

 

eg. Refreshing Artist hangs dashboard whilst a library scan is initiated

 

The initial refresh on an artist 'The communards" produces

2014-07-13 16:00:33.2206 Info - App: HttpClientManager GET: http://www.musicbrainz.org/ws/2/artist/?query=artist:"The+Communards"

 

but its not until the 2nd instance in the log (after 'the scan')

2014-07-13 16:09:33.1535 Info - App: HttpClientManager GET: http://www.musicbrainz.org/ws/2/artist/?query=artist:"The+Communards"

that the artist actually gets fetched

 

it seems that every track on every album that the artist appears is being rescanned first.

but to what end? MB3 doesnt seem to use this other track information for dis-ambiguity or better matching of musicbrainz matches?

 

https://dl.dropboxusercontent.com/u/84611964/server-63540862781.txt

 

perhaps this is the reason why artists are not automatically fetched by the scan library task, as every track of every album the artist appears in, needs to be scanned?

[speechles 1917]

Can you buy me a pony?

Edited July 14, 2014 by speechles

[ebr 14910]

I feel all warm and fuzzy inside.

[speechles 1917]

I feel all warm and fuzzy inside.

I like pie. Edited July 14, 2014 by speechles

[ginjaninja 533]

Speaking for myself, I am just reporting an experience to sensecheck it is not a bug or opportunity for improvement. Hope the feedback helps :-).