Quote:
Originally Posted by BetterRed
That database size, 61MB for 30,000 books, doesn't seem abnormal to me, others may care to comment.
Could you run calibre at the server in debug mode and post the log here?
That it is so slow when run from server suggests the server itself is the bottleneck, rather that anything related to the network.
What file system is the server running (NTFS or ??), how much memory does it have, and what other applications run at the server?
Have you tried relocating the database, as suggested in posts 3 and 4.
BR
|
OK. My server is a Core i5-4570, with 16 GB memory, running Windows Server 2016 standard edition. Two cores are occupied running a Hyper-V VM doing video conversions. The other two are doing only what a lightly loaded Windows Server does.
I did "calibre-debug -g >calibre.log" and lo and behold, startup took about 17 seconds. The log file is attached to this post.
Next I tried a normal startup of calibre, and that also took less than 20 seconds.
The library and the database are all on a local disk on this server, disk G:, not C:.
It seems that the problem has disappeared by itself. Not very satisfying.
Thanks for all your suggestions!
Bart
Bart