View Single Post
Old 06-06-2020, 02:08 PM   #24
kjdavies
Zealot
kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.kjdavies is no e-book dilettante.
 
Posts: 112
Karma: 53342
Join Date: Jun 2013
Device: Sony PRS-600
Quote:
Originally Posted by kovidgoyal View Post
Simply use the server, then the db is not re-opened on each call, it stays opened.
I tried that. By the time I load the file and set the metadata, it takes 50 seconds per title.

What I'm doing now takes 20 seconds.

On paper the server should be faster. It takes 2.5 times as long.

It does work. But it's not efficient for my purpose.

(Pretending) I sleep 8 hours a night, I can run my load scripts and load about (8*60*3=) 1440 files per night, and use calibre normally while I'm awake (and since I'm not using calibre while I'm working, I can sneak in another 8+ hours load time per day, so 2,880 files/day).

Or run via content server all day and load (24*60*6/5) 1728 files per day, and be limited to the content server web interface. This might see higher throughput overall if I can run multiple load scripts concurrently, but I haven't proven this does not slow them down.
kjdavies is offline   Reply With Quote