View Single Post
Old 07-29-2022, 05:09 AM   #10
DrChiper
Bookish
DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.
 
DrChiper's Avatar
 
Posts: 1,021
Karma: 2003162
Join Date: Jun 2011
Device: PC, t1, t2, t3, Clara BW, Clara HD, Libra 2, Libra Color, Nxtpaper 11
Quote:
Originally Posted by albell View Post
Maybe when the database is generated it already has a minimum size (and therefore the ratio is not 1: 1, even if it seems to be in your case)?
Not quite sure what you mean by this. What I did prior to indexing was issuing the DB maintenance function for that database, which "vacuumed" it and did made inconsistency checks. So the DB to be indexed was sound and minimized.

That said, my gut feeling is that how bigger the DB to be indexed is, the bigger the resulting index DB will be:
Code:
@thiago.eec -> 5.04 GB, with index DB 1.18 GB
@Drchiper   -> 6.05 GB, with index DB 4.4 GB
@Sirtel     -> 7.60 GB, with index DB 3.7 GB
What is not yet is considered is the kind of involved ebook contents, which surely has impact. Mine hardly contain pictures, but do have many words (250+ pages) So: YMMV.
DrChiper is offline   Reply With Quote