Quote:
Originally Posted by Cobalt
It's a bit of a mystery why it takes more than a fraction of a second to open a book - certainly after its initial opening. Any pre-processing that is necessary should be stored in a cache, somewhere.
|
How?
An epub is simply a zipped collection of files. It has to be unzipped. Then there are file(s) to be parsed. Then the "first" html/xml file has to be parsed and rendered.
If the ebook has all text in one file, or a very large first chapter, there is a bigger delay.
Also there are several ways a cover can be defined. Amazon tries to speed load time on azw3/KFX by skipping cover and front matter. Amazon KFX is a sort of data stream saved as a file so it can start loading during download or before a whole file is processed.
PDFs are different again and so many internals. They can be very complex and slow.
What exactly would you cache for about 16,000 epub books (which might easily fit on 32G), or even around 2,000 ebooks in about 4G flash?
How long would building the hypothetical cache take when adding 10 or 100 ebooks?
How much storage would it take?