View Single Post
Old 09-18-2012, 06:55 AM   #11
Adoby
Handy Elephant
Adoby ought to be getting tired of karma fortunes by now.Adoby ought to be getting tired of karma fortunes by now.Adoby ought to be getting tired of karma fortunes by now.Adoby ought to be getting tired of karma fortunes by now.Adoby ought to be getting tired of karma fortunes by now.Adoby ought to be getting tired of karma fortunes by now.Adoby ought to be getting tired of karma fortunes by now.Adoby ought to be getting tired of karma fortunes by now.Adoby ought to be getting tired of karma fortunes by now.Adoby ought to be getting tired of karma fortunes by now.Adoby ought to be getting tired of karma fortunes by now.
 
Adoby's Avatar
 
Posts: 1,737
Karma: 26785684
Join Date: Dec 2009
Location: Southern Sweden, far out in the quiet woods
Device: Samsung Galaxy Tab S8 Ultra
If you have custom columns that depends on other columns, then I believe all values have to be initiated when you start Calibre. I have my metadata.db on a SSD drive and still noticed this very clearly. When I deleted those columns startup was fast again.

I have my metadata.db on SSD but the Calibre library on a NAS. I use a symlink in the Calibre library to the real file on the SSD, to speed up things. Calibre became a little bit more responsive that way.

Make sure you have enough memory in the computer.

You say you have no custom columns, so that may not be the problem, unless they are hidden?

I don't believe Calibre even access the actual books when starting. Only metadata.db.

Last edited by Adoby; 09-18-2012 at 07:09 AM.
Adoby is offline   Reply With Quote