07-23-2019, 01:43 PM | #16 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@poire-z is going to be away for a few days, but he mentioned that'll he'll be looking into it when he gets back .
|
07-23-2019, 04:15 PM | #17 |
Groupie
Posts: 184
Karma: 2019866
Join Date: Feb 2018
Device: Kobo Aura-One (using KOReader app), Boox Note-3, iPad(s)
|
I've aborted it after unsuccessful 35 minutes, by restarting Kobo.
Last edited by Marinolino; 07-23-2019 at 04:30 PM. |
Advert | |
|
07-23-2019, 05:12 PM | #18 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Yeah, if it takes 10 minutes on a souped up Skylake, I really really don't encourage anyone to try on a measly i.MX6 ;p.
|
07-24-2019, 04:45 AM | #19 |
Member
Posts: 24
Karma: 10
Join Date: Sep 2014
Location: Italy
Device: Kobo Aura One
|
|
07-24-2019, 03:02 PM | #20 |
Wizard
Posts: 1,617
Karma: 724945
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
And it's hardly like my Haswell i7-4790 is a slowpoke either. Most of the discrepancy between my numbers and @NiLuJe's should be because I was using a debug build. If I'm not mistaken mine should be some 10-20% slower at most, possibly slightly higher under specific workloads.
I'd give it an absolute minimum of 100 minutes on an actual H2O/One given the numbers we posted, more likely easily twice that. (And if you run into heat-based throttling… who knows.) Hardly worth attempting unless you really want to verify whether it'll run out of memory along the way. Code:
$ inxi CPU: Quad Core Intel Core i7-4790 (-MT MCP-) speed/min/max: 1038/800/4000 MHz Kernel: 4.19.0-5-amd64 x86_64 Up: 1h 48m Mem: 5603.5/32112.8 MiB (17.4%) Storage: 3.87 TiB (54.4% used) Procs: 295 Shell: bash 5.0.3 inxi: 3.0.32 Last edited by Frenzie; 07-24-2019 at 03:04 PM. |
Advert | |
|
08-11-2019, 02:26 AM | #21 |
Member
Posts: 24
Karma: 10
Join Date: Sep 2014
Location: Italy
Device: Kobo Aura One
|
|
09-27-2019, 02:52 AM | #22 |
Member
Posts: 24
Karma: 10
Join Date: Sep 2014
Location: Italy
Device: Kobo Aura One
|
|
11-25-2019, 12:28 PM | #23 | |
Member
Posts: 24
Karma: 10
Join Date: Sep 2014
Location: Italy
Device: Kobo Aura One
|
Quote:
Why (talking about Android) apps like Moon+Reader or ReadEra can do it very easily and my beloved Koreader can't? |
|
11-25-2019, 02:02 PM | #24 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@SbAgOoTs: Chunked decoding vs. full papyrus scroll approach .
The downside being a large upfront cost, with the upside being a much smaller performance impact at runtime, as long as no layout changes are requested. |
12-05-2019, 05:03 AM | #25 |
Addict
Posts: 251
Karma: 214890
Join Date: Sep 2006
Device: none
|
|
01-10-2020, 09:49 AM | #26 |
Member
Posts: 24
Karma: 10
Join Date: Sep 2014
Location: Italy
Device: Kobo Aura One
|
Yes, even if the first run needs some minutes, ReadEra succeded in opening exactly the same test epub, whereas Moon+Reader is close to be immediate.
|
01-10-2020, 11:45 AM | #27 |
Wizard
Posts: 1,617
Karma: 724945
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
I wouldn't call anything exceeding five seconds or so very easily, but that aside.
Are you talking about KOReader on the same device as ReadEra? |
01-11-2020, 10:23 AM | #28 |
Member
Posts: 24
Karma: 10
Join Date: Sep 2014
Location: Italy
Device: Kobo Aura One
|
You are totally right. My bad choice of words.
Anyway, yes: same file, same device. |
01-11-2020, 10:54 AM | #29 | |
Addict
Posts: 251
Karma: 214890
Join Date: Sep 2006
Device: none
|
Quote:
Code:
html,body,div,span,applet,object,iframe,h1,.st,h2,.ss,h3,h4,h5,h6,p,.sb,blockquote,pre,a,abbr,acronym,address,big,cite,code,del,dfn,em,img,ins,kbd,q,s,samp,small,strike,strong,sub,sup,tt,var,b,u,i,center,dt,dd,li,fieldset,form,label,legend,table,caption,tbody,tfoot,thead,tr,th,td,article,aside,canvas,details,embed,figure,figcaption,footer,header,hgroup,menu,nav,output,ruby,section,summary,time,mark,audio,video{text-indent:0;margin:0;padding:0;border:0} |
|
01-11-2020, 01:58 PM | #30 |
Wizard
Posts: 1,617
Karma: 724945
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
It also includes rules like this:
Code:
div.east_right{width:40% !important;clear:both;float:right;margin-top:0em;margin-bottom:1em;display:inline-block} Besides that KOReader defaults to proper kerning, which is slower, it implements RTL, which may be relevant if there's Hebrew in the document, and it more correctly CSS selectors with + (I'm not sure if that makes it any slower otoh but there are an awful lot of + selectors in there which isn't exactly recommended for document performance). On a stress test like this, it could unearth some logical flaw in the support for an extra CSS selector. Anyway, as stated disabling various features would greatly improve the speed. Font kerning possibly good, but definitely not best. Render mode, probably best to go with legacy or flat. And indeed one might consider turning off embedded styles completely. (Basically either make those the default by long pressing or pre-make an SDR.) I forget, was that file ever reduced to a test case? |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Koreader in Aura H2O doesn't wake up | toodeeptofind | Kobo Developer's Corner | 6 | 03-01-2018 02:47 PM |
KOreader on Kobo Touch doesn't open an epub anymore... | sbaguz | KOReader | 8 | 04-08-2017 01:53 PM |
Koreader doesn't respond touch on Oasis | bingo619 | KOReader | 11 | 07-26-2016 05:28 PM |
New KoReader update doesn't work in my device. | the_doc | KOReader | 19 | 04-18-2016 03:10 PM |
Koreader doesn't work on 5.4.3 | vr4y | Kindle Developer's Corner | 13 | 04-15-2014 03:40 AM |