Quote:
Originally Posted by Kayadelenium
38 seconds for 77 books is a perfectly normal duration, but the software likely crashed with 18,000 books.  I need to add logging for debugging.
Tomorrow is the first day of school, and I'll likely be at the kids' school. I'll look into the error this evening and try to release a new version. |
It didn't crash. It just took rather long to run. The one error reported was a book in which I has switched to using an SVG wrapper for a full page image and did not update the manifest.
Using the numbers from the Intake library compared to the Main library, the time is about right. The Main library has a higher percentage of omnibuses since I have a habit of converting a completed series into an omnibus volume.
Edit: Reran the epubveri library test while not running a collection of VMs running in the background and the time for the check dropped to 1hr 29 min. Having that mix of Windows and Linux VMs updating was not that big a CPU load but they keep the disk usage about 80%. Gave the computer something to do while I was watching the CFL Labour Day classic games.