Processing power required for UPnP control point

[DavidL]

(23-11-2017 23:02)DavidHB Wrote:  @DavidL

It's interesting that you describe a browse sequence which includes an albums listing, as that will make extensive use of album art. Bubble caches album art, and you might like to discover how large that cache is (via Settings > Apps > Storage).

The time required to search a large cache for a fairly large number of images might be a factor. That can be tested by clearing the cache, which is arguably a good maintenance practice in any case. Of course, if you use a browse sequence requiring the retrieval of a large amount of album art from the server immediately after clearing the cache, that will tend to slow things down.

I use BubbleDS, which is similar to BubbleUPnP in most respects, and tend to narrow down my browsing range (for example using Genre > Composer > Composition) before getting an album list; that will, I suppose, limit the amount of album art Bubble needs to access and cache. When I had a Nexus 7 (also 16GB, and usually with less free space than you have), I didn't encounter any particular speed issues. My library is smaller than yours, but I'm not sure whether that is a relevant factor; my guess is that what matters is not the size of the dataset on the server, but the amount of data the control point actually has to access. Simon may, of course, be in a position to advise differently.

David

Thanks DavidHB

I had 6900 files in the cache using 160MB of storage. Clearing this has dramatically improved the response time - I guess all of this cache is searched for relevant cover art. Mine may be a special situation as nearly all of the cover art I have is for Jazz, Popular and World music, with very little for classical music, so the search in the cache is likely to be a waste of time when classical music is requested.
David