Quote:
Originally Posted by Cobalt
snip
I don't think you quite understand what a cache is (or can be).
It is an area of storage where you store information that you think may be used in the near future.
|
You might think that, but you'd be wrong. The kind of cache that is common is indeed information that's just used and might be needed again now. That would only at all apply to re-opening the same ebook you just closed. That may exist. It wouldn't solve the problem, if there is a problem. So I considered if the starting information to open all books could be cached.
A Kindle in general is much slower with PDFs and no faster at all for Azw3/KF8 or mobi/KF7, if everything is equal. Many are slower to wake or load a non-KFX ebook. I'm not sure about KFX because I haven't used those in a long while and have none.
A Kobo Sage is less than 1 second to open ebook from sleep.
At worst 4s to reopen same ebook at the cover and about 1s or less to reopen it or open another book.
So loading the cover can take 3 to 4 seconds (1072 x 1430). A kindle by default skips the front cover.
So indeed any properly formatted epub, not being opened at the cover, is probably less than 1s on my Sage. The Libra 2 I have seems slower at about 3 seconds.
I can't see how a conventional cache, or the less common cache table of all ebooks can help at all.
The cover size and structure of the epub has more impact. Also PDFs are very variable and worse on any Kindle I've tested (K3, DXG, Basic, PW1, PW3, PW4, Oasis (2nd version).
If people are seeing really slow opening epubs it's either got a giant cover or bad structure or both.
So my conclusion after testing right now is that there is no problem.