I don't mean just rendering performance, I also mean pagination performance. I know for example that SONY's LRF layout routine is extremely fragile. I can easily create LRF files that are correct, but cause the reader to reset because it runs out of memory. And LRF is really, really simple compared to HTML.
And pagination takes a hell of along time for larger books. You wont notice this if you use connect, but if you transfer directly to a reader, then the hit is significant. I've often had to wait for upto 15mins for the reader to finish pagination.
|