Bug 12866 - Alarms don't page playlists in SlimJON; can lead to excessive load times.
: Alarms don't page playlists in SlimJON; can lead to excessive load times.
Status: NEW
Product: Logitech Media Server
Classification: Unclassified
Component: Alarm
: 7.4.0
: PC Other
: P3 normal (vote)
: 8.0.0
Assigned To: Michael Herger
: ipeng
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-15 00:56 UTC by Joerg Schwieder
Modified: 2009-10-12 07:55 UTC (History)
2 users (show)

See Also:
Category: Bug


Attachments
Log file of a single "Alarm Sounds" menu (139.40 KB, text/plain)
2009-07-15 01:09 UTC, Joerg Schwieder
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Schwieder 2009-07-15 00:56:48 UTC
I'm getting reports from some iPeng customers with large numbers of playlists that the "Alarm Sound" menu loads forever.
(see https://trac.penguinlovesmusic.de/trac/ipengnat/ticket/93)

The reason for this, IMHO, is that the "Alarm Sounds" menu is loaded at once including all of it's submenus (the actual playlists are in a submenu to "Alarm Sounds" and since "Alarm Sounds" only contains a few items this doesn't get paged.

I suspect this will be the same on the controller and SqueezePlay, iPeng just uses the normal SlimBrowse menu.

A solution IMHO would be to load the submenus separately (with a separate request), at least the "Playlists" submenu since it could be paged then and the delay would not affect the other submenus and the main "Alarm Sounds" menu.
Comment 1 Joerg Schwieder 2009-07-15 01:09:20 UTC
Created attachment 5463 [details]
Log file of a single "Alarm Sounds" menu

OK, looks like it's not only the Playlists but also the Favorites that get pulled into this monster menu.

I attached a sample log from my server. Plese not that I only have a few playlists and very few favorites, yet this is still a monster of a menu.
This is ONE menu and get's loaded at once.
Comment 2 Ben Klaas 2009-08-26 07:53:03 UTC
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Comment 3 Michael Herger 2009-09-03 07:37:06 UTC
As I came up with that code I'll probably have to fix it too...
Comment 4 Michael Herger 2009-10-12 07:55:41 UTC
I'm sorry, applying new targeting guidelines