SqueezePlay actually requests browse lists in chunks of 200 items ad the server only fetches the data in these chunks.
The WebUI requests the entire list and then decides how many to show based upon the paging parameters (including alpha-bar). It has always been this way but in onebrowser all the data for the entire list is fetched and processed to some degree, before the final processing is limited to just the chunk to be displayed. In trunk, less of the complete query is fetched before the chunk is selected. This means that for the WebUI it is to be expected that there may indeed be performance regression, especially with large query results. It would be possible to rewrite the WebUI to fetch the page-bar up front and then make a chunk-size restricted query but this would be a significant piece of work. -- awy ------------------------------------------------------------------------ awy's Profile: http://forums.slimdevices.com/member.php?userid=7480 View this thread: http://forums.slimdevices.com/showthread.php?t=85895 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
