I'm curious. I don't have a bazillion ebooks, so am asking those who have a pile of them on their readers. I have only around 234 titles on my Glo, with some distributed over 11 shelves. But some are a bit ponderous, the one I'm making my way through now has 4,443 pages according to the reader. Anyhow, I'm not noticing anything out of the ordinary -other than it taking a few seconds to open this huge book from the home page carrousel, but wondered what is causing the problem with larger collections.
Is it because of cover image processing? Do you see a major difference in performance when looking at the shelves view with small icons vs. the larger covers without the text? (Wrench option menu on individual shelves and the books choice in the Library)
Is it because there are in some cases several thousand entries in the database to be processed? Is it because they make sure all the cover images are rendered before displaying the first page of items on a shelf or in the Library? Perhaps code that only prepared the covers for a page or so in advance would limit the initial lag time and allow for further processing as pages were advanced. This, of course, assumes they have multi-threaded or multi-tasking capability so a background task could continue to process items while pages of shelves or the Library are advanced, or that short waits beat one really long wait?
If it's sorting the database, why don't they include index fields for their different sorts as a series of linked lists and just re-sort the index, really just insert or delete, as titles are added or deleted?
I'm just trying to get a handle on why it slows down with so many books beyond what seems proportionate for the number of books. I mean a 1GHz processor is a lot of oomph all in all.
Or is it really not the code so much as processing problems with certain books?
Last edited by TechniSol; 05-22-2013 at 10:41 PM.
|