View Single Post
Old 06-14-2020, 02:56 PM   #3
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
If you make a lot of metadata changes via various plugins, you will see that the metadata.db file will grow enormously due to unclaimed SQLite database space.

Real example statistics from a SQLite browsing tool that does a compress:

Before compacting<<<----------->>>After compacting:
Page Count = 118,342<<<---------->>>Page Count = 3,606
Database Size = 121,182,208 bytes<<>>Database Size = 3,692,544 bytes

So, the metadata.db file went from over 121mb to less than 4mb in size.


If you have many Libraries, and if you use Job Spy, there is a menu option under "Utilities" named "Vacuum/Compress metadata.db [All Other Libraries]". It vacuums all except the current Library which is open in Calibre at the moment. Libraries must be "closed" to be vacuumed.

Remember to make periodic full backups of all of your Libraries, and also before doing anything en-masse.



DaltonST
DaltonST is offline   Reply With Quote