Yannzola wrote: > I love the new Custom browse plugin! Only annoyance I've noticed so far > is the rather long time it takes to display certain items... for > instance displaying Albums\Artists\Genres can take over 15-20 seconds > to show. Sometimes even longer... sometimes minutes.
Without looking into this much further, this is probably down to indexing, or rather, the lack of it. The slimDB will have been created and optimised for the standard slimserver query operations. One of the downsides to adding the ability to have custom browse modes is that not all of them will be optimal. There are a couple of possible solutions. 1. You could modify the slimDB definition to add index to speed up your custom browse modes. 2. SlimDB could be completely re-factored to store all tags in one "attributes" table, keyed to the tracks table. e.g. id track_id attrib_name attrib_value Where: id - unique id for this relation track_id - track to which this relation belongs attrib_name - name of tag, e.g. Genre, Artist, etc. attrib_value - the value of the tag, e.g. "Rock", "AC/DC" The advantage to this approach is that it makes it possible to search/browse/organise by pretty much anything. And the table can have the necessary indices to make it perform well. R. _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
