3. just browsing or changing pages in navigation is slow and sometimes unresponsive.
I looked into this using Erland's 100k collection. And I figured out there were two issues here:
- first, getting the data and render it into HTML takes some time. On my dev machine with SSD this could easily be 3-4s per page. I would imagine a NAS would take... much longer.
- second, the browser has to render that HTML on screen. Depending on the number of items to be displayed this is taking suprisingly long even on my MacBook (admittedly soon to be 4yrs old).
The first case we can tackle with some aggressive caching of browse pages. They hardly ever change between scans - why should we render them over and over again?
The second issue is harder to address. A new web UI could work wonders. But that's a massive amount of work. That's rather unlikely going to happen. That said the delay in the browser in my test case was much smaller than the delay server-side. Add to this that in most cases the client would be much more powerful than the server-side, addressing the server might be a good start.
-- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
