MobileRead Forums - View Single Post

chaley · 07-18-2021, 09:42 AM

For calibre, 12,000 books isn't that many but it could matter depending on the computer you are using and where the library is stored.

First question: have you ever waited for some time to see if calibre becomes responsive again?

When you save a template function, calibre resets its internal data so that any usages of the changed/new function will be taken into account. The reset forces rereading of the database. The speed of this process is mostly determined by a) how the library is sorted, b) whether there is a virtual library active, and c) whether the computer has enough memory to compute everything necessary. In your case:

How is the library sorted? Is it a complicated sort using composite columns (columns built from other columns), especially those that touch the disk to get information about formats?
Do you have a VL active?
Are you running 32- or 64-bit calibre? It is hard to imagine that this matters, but it might.

Last question: have you run it in debug mode? I doubt it would show anything but one never knows.

Last suggestion: sometimes the calibre database gets quite large as it collects detritus from change operations. An overly large library database can be slow. Running Library maintenance / Check library (click on the Library button to see this choice) will compact the database. You don't need to run "Check if files" step (but I would just to see).

07-18-2021, 09:42 AM	#7
chaley Grand Sorcerer Posts: 12,476 Karma: 8025702 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	For calibre, 12,000 books isn't that many but it could matter depending on the computer you are using and where the library is stored. First question: have you ever waited for some time to see if calibre becomes responsive again? When you save a template function, calibre resets its internal data so that any usages of the changed/new function will be taken into account. The reset forces rereading of the database. The speed of this process is mostly determined by a) how the library is sorted, b) whether there is a virtual library active, and c) whether the computer has enough memory to compute everything necessary. In your case: How is the library sorted? Is it a complicated sort using composite columns (columns built from other columns), especially those that touch the disk to get information about formats? Do you have a VL active? Are you running 32- or 64-bit calibre? It is hard to imagine that this matters, but it might. Last question: have you run it in debug mode? I doubt it would show anything but one never knows. Last suggestion: sometimes the calibre database gets quite large as it collects detritus from change operations. An overly large library database can be slow. Running Library maintenance / Check library (click on the Library button to see this choice) will compact the database. You don't need to run "Check if files" step (but I would just to see).