Thread: Firmware 4.7.10413 -word finding bug?
View Single Post
Old 01-31-2018, 07:03 PM   #17
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by minsik View Post
thanks for good help attempts.

In calibre edit and check book it shows this error.
-------------------------------------------------------------------
This HTML file is larger than 260 KB. Too large HTML files can cause performance problems on some e-book readers. Consider splitting this file into smaller sections.
-------------------------------------------------------
now need to spit into new sections. Not getting very far yet.
Others have expressed an opinion, but, I have only seen two issue with files larger than this. Firstly, there is an page break added somewhere in the file. I'm guessing that the firmware is dividing the file up into smaller chunks and handling these as separate files for rendering. I don't know at what file size it starts to do this.

The other is performance. The larger the file, the slower the performance as you progress through the file. At the start, it is fine, but as you go through it, the page turning slows down. My test for this was a book with 30 chapters that I merged into on. I think it was 3MB uncompressed. But, it wasn't until I was halfway through this that the performance drop was noticeable. I don't think it would be for a 300KB file.

One thing I don't know is how it affects the search. If the large file is being split in memory by the firmware, it might have the problem you started the thread about. I doubt if I ever tested search.

Overall, I split the internal files on natural boundaries like chapters. But, if there aren't any chapters, or if one is a bit bigger, it doesn't worry me much. It doesn't break the device and I would prefer not to add artificial divisions.
davidfor is offline   Reply With Quote