View Single Post
Old 06-11-2013, 05:30 PM   #128
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,450
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by TechniSol View Post
The other question, and it's a good one, is why are those sqlite databases so large? Based on the size reported by one poster for a given number of books they are storing 40KB on average per book? What is all that, and is it why it appears accessing the DB takes so long? That's a lot of space to store a book title, path, current page, some reading stats, and some metadata... so what else are they bogging the Db down with? If it's annotations or the like, reference them by storing a path and filename and dump them into their own text files already.

These are portable devices, they should be lean and mean and so should the databases.
Quite a bit of the space is taken up by information on the chapters within a book.

Regards,
David
DNSB is offline   Reply With Quote