Quote:
|
That said...just an observation, but speed has NOT been one of the strengths of KOReader since I've been using it. Quite the contrary really; I've found it to be frustratingly slow when opening larger books (but it does ok on books of more common sizes, so this is not an issue with most books).
|
It's not really a book size but a number of nodes problem. You could create a relatively small book that'd bring crengine to its knees.
Nickel could be faster at parsing an EPUB, but I would suspect that Nickel is primarily a bit more clever about what it actually does when loading a book. Since an EPUB is normally divided into multiple XHTML files, you shouldn't need to render more than one or two at once. (The downside being you wouldn't have reliable page numbers/percentages.)
In PDF/DjVu this works out better in KOReader. The current page is shown, while the next page is rendered into memory.
Quote:
|
These tasks, along with searching a book's contents, are the most common things I do that test an app's speed.
|
That's a very narrow definition of speed.
