View Single Post
Old 01-10-2015, 02:40 AM   #640
AcidWeb
KCC Co-Author
AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.
 
AcidWeb's Avatar
 
Posts: 845
Karma: 765434
Join Date: Mar 2013
Location: Poland
Device: Kindle Oasis 2
It is more like artificial boundary.

Kindlegen maximum output file size is 650MB. KCC code don't have any size limits. But after extensive research I noticed that in many cases so big files cause big Kindle slowdown (even on newest ones). So unless you want spend 3+ seconds to turn page creating so big files is not very good idea. Even 400MB files are already somewhat effected by that slowdown.

Additionally I consider 650MB files are not practical considering that a large part of Kindle users have only ~1,25GB storage on their devices.

In current version splitting of MOBI output is not optional and you can't disable it without code modification.
AcidWeb is offline   Reply With Quote