Quote:
Originally Posted by HarryT
Oh, OK.
The reason, BTW, I say that Calibre conversions appear to me to be CPU limited is that I always have Windows task manager running in a corner of my screen, and when a conversion is running, the "Calibre worker process" thread is at 25% CPU (ie it's running one of the four CPU cores flat-out), whereas disk usage never seems particularly high. But perhaps it does vary with the type of conversion, as you say. Nearly all the conversions I run are ePub to AZW3.
|
Mine was xhtml to ePub albeit one with hundreds of chapters. Granted, that was in VM with both the library and /tmp on the same drive. With /tmp on SSD and the Calibre library on HDD, the script probably would've worked fine.
Another thought, my library's not made up of typical books. There's a bunch of drabble fics that are 1K words or less. Should take very little CPU time to convert but small block read/write is something HDDs are slow at.
Right now, I duplicate a 4000 book library maybe 3x a day as I work on adding and cleaning metadata (thank goodness for TXT query on the MCS plugin). That's ~12,000 small files copied every time (epub, txt, jpg, opf).