KOReader doesn't open large, complex ebooks? - Page 3

Frenzie · 01-11-2020, 04:20 PM

@poire-z reminded me that investigative results are here.

Removing just one of the CSS files from the document may significantly aid performance without affecting looks. They're virtually identical, but of course double the CSS also doubles CSS application time.

SbAgOoTs · 01-13-2020, 08:44 AM

First, thanks for all your efforts to solve this issue!

I made some tests based on your suggestions and I confirm everything you noticed:

1) deleting all the CSS files brought the opening time to around 1 minute;
2) then, excluding any incorporated style (or probably because it's not the first opening...) brought it to some seconds.

Perfect!

As you mentioned in the discussion with poire-z probably the best would be to have an automatic tool cleaning unused, bloated or simply slowing down CSS...

SbAgOoTs · 01-13-2020, 08:45 AM

Quote:

Originally Posted by Frenzie

I forget, was that file ever reduced to a test case?

I don't know what you mean...

Frenzie · 01-13-2020, 12:40 PM

That wasn't really aimed at you specifically.

A problem like this can always be reduced to a smaller testcase. Normally that's for clarity, but in this case it'd also simply be for speed. Cutting out all but the first few Bible books should display the same behavior (including all of the potential performance issues) without taking 20 minutes for analysis.

If I hadn't done that already, it's something that could be worth investigating. But since I'd already done it, it's probably not worth repeating.

01-13-2020, 08:44 AM	#32
SbAgOoTs Member Posts: 24 Karma: 10 Join Date: Sep 2014 Location: Italy Device: Kobo Aura One	First, thanks for all your efforts to solve this issue! I made some tests based on your suggestions and I confirm everything you noticed: 1) deleting all the CSS files brought the opening time to around 1 minute; 2) then, excluding any incorporated style (or probably because it's not the first opening...) brought it to some seconds. Perfect! As you mentioned in the discussion with poire-z probably the best would be to have an automatic tool cleaning unused, bloated or simply slowing down CSS... Last edited by SbAgOoTs; 01-13-2020 at 11:38 AM.

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

01-11-2020, 04:20 PM	#31
Frenzie Wizard Posts: 1,619 Karma: 724945 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	@poire-z reminded me that investigative results are here. Removing just one of the CSS files from the document may significantly aid performance without affecting looks. They're virtually identical, but of course double the CSS also doubles CSS application time.

01-13-2020, 12:40 PM	#34
Frenzie Wizard Posts: 1,619 Karma: 724945 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	That wasn't really aimed at you specifically. A problem like this can always be reduced to a smaller testcase. Normally that's for clarity, but in this case it'd also simply be for speed. Cutting out all but the first few Bible books should display the same behavior (including all of the potential performance issues) without taking 20 minutes for analysis. If I hadn't done that already, it's something that could be worth investigating. But since I'd already done it, it's probably not worth repeating.