Quote:
Originally Posted by iandol
@NiLuJe: wow, that is a great description of what is going on, I understand this much better. I tend to read larger academic books (my current one is 4496 pages according to Plato), and so probably am pushing KOReader against its advantages.
|
The number of pages doesn't necessarily matter that much. It's more the number of HTML elements and the complexity of the CSS.
Of course any document over a thousand pages will have quite a number of elements by logical necessity, but you can fairly easily create a 10-page document that'll do as bad or worse as a 1000-page one if you (don't) know what you're doing.
Btw, you can always share the document using
ScrambleEbook if it's not open access.
Quote:
Originally Posted by iandol
Do you know how long this cache is utilised (does KOReader have a cache policy?), and how many books KOReader can cache on what I assume is something low-specced like the Kobo Nia? Will it cache till RAM runs out?
|
The most important cache in this context is written to files, in cache/cr3cache.
The default max size for that is 64 MB, but you can set it higher, um, somewhere.
What that means in number of books depends on the books. Your average book will generate a cache of about .25 to 1 MB in my experience, so I'd be inclined to phrase 64 MB as at least 64 books. But your specific scenario will doubtless generate a much larger cache file.