View Single Post
Old 07-23-2016, 10:27 AM   #26
HarryT
eBook Enthusiast
HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.
 
HarryT's Avatar
 
Posts: 85,556
Karma: 93383099
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
Quote:
Originally Posted by compurandom View Post
Programming tricks might help, but I do think a faster processor would help more.

I mean, my0 epub and kepub books turn just fine.
What's killing me is the high res scanned pdfs that have +10 second per page turn times.

I've got a few vectorized PDFs that also are bad, with complex line drawings that seem to take forever to render.

So, yes, you are right, on the majority of books meant for ereaders, the cpu is fine. But if you get a bigger screen, people are going to want to read more PDFs, and that will need a faster cpu.
It's a compromise between CPU speed and power consumption: the faster the CPU, the higher the power consumption. As you say, CPU performance is optimised for ordinary novels, and really is too slow for complex PDFs. That's why I read novels on my Kindle, but PDFs on my iPad, which does have a fast CPU.
HarryT is offline   Reply With Quote