Quote:
Originally Posted by BetterRed
Do you know why this library takes a long time to open?
Whilst 80,000 books is large I wouldn't consider it as being VERY large, I have a library with 143,000 books that opens in a few seconds which I don't regard as a LONG time.
BR
|
@BetterRed
I wish I knew. I too would think that 80,000 wasn't so bad. it used to be around 100,000 until I changed some ways of managing and split off some. It helped some until this one continued to grow. The larger is a mix of actual book entries and just metadata record entries (with covers). I do keep opfs in the book files also.
I'd rather the two libraries be combined with Virtual Lib's as the management method. Now, I have to duplicate the various rules between the two (library specific stuff). Still, especially with this new shortcut, it's been better to get to that group and not have to wait for the large to load unless I've forgotten and left it as the last open.
I can attest to this holding true even after the computer was wiped and Calibre and the library restored. It has taken progressively longer as it grew. This does, however, coincide with the various updates pre and post Calibre 2.0. But the small library opens almost immediately.
I've tested this many times with only necessary programs running and nothing in the background that also isn't necessary.
It takes more RAM to open as it gets larger. The metadata.db is 382mb.
The smaller, split-off one is only 13.2 mb. It opens quickly.
I've watched the Task Mgr for memory and cpu usage when these open.
At one point, the large one consistently took about 800,000 K of memory to open and stayed around that unless jobs were running.
That grew to about 1,000,000. Then 1,100,000. And now it hits about 1,300,000 K before it opens and stays there. That last 200,000 goes really slow but the CPU usage stays low around 35% and the memory around 65%. NOTE: this is with Chrome open and many tabs.
However, the last small part of the opening time/memory runs the CPU up and the memory to almost 100%.
Then, once open, it "settles" back to 21%CPU and higher memory usage since it's open (with Chrome). I cannot recall the number without.
I'm running an Intel i3 2.1Ghz with 8gb ram and 64-bit. While I'm sure a better setup would help, the only software that has been changed since buying it is Calibre.
The same 'longer opening time to larger library' held true on my pre to early 2.0 copy on a Pentium with 4gb of RAM and nothing else running. I don't even bother with Calibre on that one with anymore.
Calibre opens "in a flash" with the smaller library. Hit 245,000K memory and that's it. This is also with Chrome running the same.
I may be wrong, but it actually seems to be faster with these new shortcut paths. Again, could just be perception at the moment.
If you have any thoughts on why this is, i'm open to them. Thanks!