KOReader is blazing fast

[Frenzie]

Speaking of delay, I just came across this today:

https://blog.wooting.nl/what-influences-keyboard-speed/

[Frenzie]

Originally Posted by NiLuJe

The difference? A real eMMC chip on the Forma vs. the insane internal SD card design on the H2O. It's sure nice on the hackability front, but, man, is it awful in terms of performance.

Even after the first load? I'd expect it to hang around in memory.

Originally Posted by NiLuJe

For instance, mine is fairly consistent on a fresh, cold boot, and then starts to go wonky at the first sleep cycle. Although, "fairly consistent" might be stretching it, because it tends to stick the other way around after a cold boot (meaning stick to the highest clock speed even when idle).

Yeah, occasionally I notice oddly slow page turns where I can only assume it's the scheduler underperforming. But oddly slow as in it takes 100 ms instead of 20 ms (or whatever), so still a lot faster than Nickel. :P

[heyman]

@Frenzie @NiLuJe

please correct me if I say something wrong.

I still believe koreader running on simple linux (kobo, kindle) could be faster (like faster page turning) than android version. Because android is a over-big, over-messy architecture. Android itself is an "app" running above the linux (kernel), and we run our apk on the android (java), android is actually a VM, this casuses more delay than anything else.

[Frenzie]

Originally Posted by heyman

I still believe koreader running on simple linux (kobo, kindle) could be faster (like faster page turning) than android version. Because android is a over-big, over-messy architecture. Android itself is an "app" running above the linux (kernel), and we run our apk on the android (java), android is actually a VM, this casuses more delay than anything else.

I don't think that's necessarily true provided you've got enough RAM, but Android doesn't really have much to do with anything. Nickel is the same principle as KOReader (or coolreader or Plato). Just a fullscreen app running on embedded Linux.

[pazos]

Originally Posted by heyman

@Frenzie @NiLuJe

please correct me if I say something wrong.

I still believe koreader running on simple linux (kobo, kindle) could be faster (like faster page turning) than android version. Because android is a over-big, over-messy architecture. Android itself is an "app" running above the linux (kernel), and we run our apk on the android (java), android is actually a VM, this casuses more delay than anything else.

No, android is not an "app". It is a framework based on multiple services/daemons running.
No, the Dalvik/Art virtual machines don't cause any noticeable delay.

[BloodRagg]

Ahh a new version, is there a way to debug lag of page turns ?
With me its mostly high resolution pics being rendered to my devices resolution.
But Im interested any way.

[Frenzie]

Depends a bit on what you mean by debug, but either way the emulator would be the way to go unless there's a clear indication that there's something ARM-specific going on.

For LuaJIT, cf. https://www.freelists.org/post/luaji...filer-released

For regular gdb stuff I like the Nemiver frontend, but anything goes. :P See https://github.com/koreader/koreader...with-gdbserver for doing it on-device.

I've done my profiling on crengine with cachegrind + KCachegrind for visualization. That resulted in some pretty significant performance gains (mostly thanks to @poire-z ).

[BloodRagg]

Originally Posted by Frenzie

Depends a bit on what you mean by debug, but either way the emulator would be the way to go unless there's a clear indication that there's something ARM-specific going on.

For LuaJIT, cf. https://www.freelists.org/post/luaji...filer-released

For regular gdb stuff I like the Nemiver frontend, but anything goes. :P See https://github.com/koreader/koreader...with-gdbserver for doing it on-device.

I've done my profiling on crengine with cachegrind + KCachegrind for visualization. That resulted in some pretty significant performance gains (mostly thanks to @poire-z ).

Whattttt all I can say is