Koreader speed: Kobo Forma vs. Pocketbook Inkpad 3

[svkytbsld]

I have Inkpad 3 and I am using Koreader on it for pdfs. But as you may guess, the speed is terrible. It's very sluggish.

So, I have started to think about getting a Forma. it has +0.2 inch benefit and can be much speedy.

The question is, is it? How is Koreader performance of Kobo Forma? I tried Koreader on Libra 2 and it was amazing. May be Forma is good also...

[NiLuJe]

The Libra 2 uses the exact same SoC as the Forma. The only difference is the screen tech, which is... different (previous generation but plastic for the Forma, newer generation but glass for the Libra 2).

Given that PDF workloads are much more heavily tied to the SoC's performance than the screen's, I don't except any meaningful difference between the two (unless you're an eink nerd).

[svkytbsld]

Originally Posted by NiLuJe

The Libra 2 uses the exact same SoC as the Forma. The only difference is the screen tech, which is... different (previous generation but plastic for the Forma, newer generation but glass for the Libra 2).

Given that PDF workloads are much more heavily tied to the SoC's performance than the screen's, I don't except any meaningful difference between the two (unless you're an eink nerd).

Thank you so much for this precise info. That counts a big plus for Forma...

What about your subjective experience? Is Forma a good device for Koreader (especially comparing PB)? Can you advice another 7.8"+ device for a speedier Koreader?

[NiLuJe]

The Forma is an *excellent* device, bar the dreaded sidebar of suck lighting issue. Probably still my favorite, despite the much beefier SoC & performance of the Sage.

[VladimirS]

I am using 2022.10. version (https://github.com/koreader/koreader...s/tag/v2022.10)
and PDF performance is very, very good.

My PDF-s are scanned books (around 300-500 pages) and around 30-50 MB.

Keep in mind that eink display have intrinsic permormance limits, in terms
of display refresh time which is around 0.4 S and does not include any
additional cpu time for processing of data before displaying it.

So, I can recommend Inkpad 3 for Koreader 2022.10. "Muhara" version .

[pazos]

Every device is great compared to Pocketbooks regarding speed.

But even pocketbooks can be a bit better than with stock settings.

By default KO uses the same waveforms the stock reader is using. They're slow also on PB reader.

IIRC there's a setting to changing waveforms. It is tuned for "max quality", you can try the setting just below that. You'll gain some speed and loose some quality. There're a few more settings but they're, IMHO, utterly unusable.

[NiLuJe]

@pazos: IIRC, the "waveform modes" settings are no longer applicable now that we're using InkView for refreshes.

(The code is still there though, as is the hardware rota stuff on the few devices @ezdiy had).

PB's a mess.

[pazos]

Originally Posted by NiLuJe

@pazos: IIRC, the "waveform modes" settings are no longer applicable now that we're using InkView for refreshes.

(The code is still there though, as is the hardware rota stuff on the few devices @ezdiy had).

PB's a mess.

Oh, that's a pitty.

Indeed PB is a mess. At least we're doing it as good/bad as stock as far as eink refreshes.

[cellaris]

Originally Posted by VladimirS

I am using 2022.10. version (https://github.com/koreader/koreader...s/tag/v2022.10)
and PDF performance is very, very good.

My PDF-s are scanned books (around 300-500 pages) and around 30-50 MB.

Keep in mind that eink display have intrinsic permormance limits, in terms
of display refresh time which is around 0.4 S and does not include any
additional cpu time for processing of data before displaying it.

So, I can recommend Inkpad 3 for Koreader 2022.10. "Muhara" version .

My experience matches yours, both on the InkPad 3 and InkPad X.

[cellaris]

Originally Posted by pazos

Every device is great compared to Pocketbooks regarding speed.

I still think that the performance of KOReader when reading a book is very similar on any compatible device, and the speed differences are minimal. PocketBook is no exception.

I leave a comparative video as an example...

https://drive.google.com/file/d/1og3...w?usp=drivesdk

[VladimirS]

Great video, Cellaris !
Thanks for that.

[Hyphen-ated]

Originally Posted by cellaris

I still think that the performance of KOReader when reading a book is very similar on any compatible device, and the speed differences are minimal.

On a Kobo Aura HD, I measured KOReader to take on average .6 seconds to turn a page in an epub. On a Kobo Forma that dropped to below .2 seconds

I consider that a pretty big difference

[cellaris]

Obviously there will always be devices that are faster than others in running KOReader, but the differences in tenths of a second are not perceived as slow. Turning pages, opening the dictionary, underlining a text, searching in the book, accessing the table of contents or bookmarks, turning several pages or chapters by gestures or touching the screen... All this (which is not done at the same time, but throughout the reading process) is perceived as being done immediately, not slowly, regardless of whether it takes a few tenths of a second longer with one device than with another. When I turn a page with the Tolino Shine 3 (after reading that page for a minute) I know that it takes longer than with a Kobo Clara HD, but when I am reading I don't perceive that slowness. What I perceive is that the page turns immediately. In my opinion these differences in tenths of a second (if they exist, because they do not always exist) are in practice irrelevant and do not affect a satisfactory reading.

What does feel slow when using KOReader is what takes several seconds to execute: opening a large book for the first time, changing a font or its size, changing the line spacing or margins.... This is indeed slow and sometimes very, very slow. (Curiously, this obvious slowness is accepted as a "lesser evil", even by those who are so concerned about speed).

But it is not my intention to elucidate which device is faster in running KOReader, but to point out that the basic configuration (what we do when we read a book) is the same on any device and that the differences at user level are not as important as sometimes indicated. And that the operation of KOReader cannot be separated from our tastes and needs. The best example is to read those forums where the million dollar question is asked: "which is the best device to use KOReader on". Every user offers a different answer (and, in my opinion, they are all right). So my advice is invariably the same: don't look so much at the performance of KOReader, but at the features of the device. If there are features that are important to you, choose the device that best suits those features, regardless of the device brand.

[NiLuJe]

Originally Posted by cellaris

All this (which is not done at the same time, but throughout the reading process) is perceived as being done immediately, not slowly, regardless of whether it takes a few tenths of a second longer with one device than with another.

Not for everyone. I am *extremely* sensible to UI latency, and, yeah, I *will* notice a difference as early as ~75ms.

(You can also put me in the group of people that will murder "smooth motion" algorithms out of every TV they can find, because it's an abomination; and that sensibility applies to on-screen motion judder, too).

[Hyphen-ated]

Originally Posted by cellaris

What does feel slow when using KOReader is what takes several seconds to execute: opening a large book for the first time, changing a font or its size, changing the line spacing or margins.... This is indeed slow and sometimes very, very slow. (Curiously, this obvious slowness is accepted as a "lesser evil", even by those who are so concerned about speed).

Well, I open a large book for the first time once, and I turn a page of that book maybe 1000 times. So it is a lesser evil for the thing that happens 0.1% as often to be slower.

For me a .6 second page turn feels "tolerable but not great" while a .2 second one feels "quite good". it's very noticeable.

as a person who doesn't notice the difference, you have less need to prioritize a reader's page turning speed when making a decision about what to buy, because for you those differences feel minimal.

But it's not really helpful to go around telling people those differences are minimal, as if that were true for everyone. if the person you're advising is more perceptive than you, you're giving them bad advice.