Quote:
Originally Posted by davidfor
There are also writes to the database while reading. The current position is store plus events such as page turns. But, I have no idea when this is done. It could be for every page, or when the book is closed.
|
Even if it's done at every page turns, the bottleneck there is CPU, GPU, ereader screen and how page turning is coded.
Improving browser I/O speed may make sense if you want to use Wikipedia offline, as discussed in other threads. But IMHO the real problem in Kobo performance is 1) the hardware 2) the code quality.
Anyway you can try to
monitor I/O usage and see if there's really an intensive use that justify the effort.