View Single Post
Old 10-18-2019, 07:04 AM   #7
mbovenka
Wizard
mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.
 
Posts: 2,079
Karma: 14079267
Join Date: Oct 2007
Location: Almere, The Netherlands
Device: Kobo Sage
Quote:
Originally Posted by BetterRed View Post
Caveat - calibre reads the database into memory when a library is opened, so relocating it won't make much, if any, difference.
Yep. All readonly activities get done on the in-RAM DB image, so searches and such are not impacted at all by the speed of your storage.

My metadata DB is about 600MB, and when I migrated to SSD Calibre's startup time decreased by a few seconds, and anything that updates the database became faster (sometimes by a lot: 'calibredb backup_metadata', which obviously writes a lot of very small files, became about 15 times faster), but search speed, where the OP's issue is, did not change.

So, to the OP: don't bother. If searches take too long, the bottleneck is not your disk, but CPU and/or RAM. If you're not already doing this, make a habit of restricting your searches, like 'title:<blahblah>' or 'authors:'blahblah'. Calibre then only searches that table instead of the entire metadata database, and that can make a significant difference.

Last edited by mbovenka; 10-18-2019 at 07:14 AM.
mbovenka is offline   Reply With Quote