[andrewburt]

Hi, all, I noticed that converting the same .epub file to a .mobi inside the app (win10 PC) took 7 minutes. I then converted a copy of the same .epub using "ebook-convert" via the command line (same PC, in a separate, empty directory, so no involvement with the original files)-- and it took 1 minute. (Same results if I do it in the reverse order, so it isn't a caching kind of thing.)

I compared the job log outputs (using the -v -v -v option on the command line), and they are essentially the same. (The semi-random output order of the internal xml files are displayed in two different random orders, and some options that say 'None' show as '' empty, or 0.0 vs 0, or for search_replace, '[]' vs None, but I can't imagine those being meaningful.) All the settings are essentially the same. There's no smoking gun showing.

I've repeated this on different books, same result: In app takes waaaaay longer than command line.

This is for version 2.44.1.

When watching the in-app log, it has particularly slow points (e.g. ~1+ minutes each) at "Flattening css and remapping font sizes", "Parsing manglecase.css", "converting xhtml to mobipocket markup", and "compressing markup content." When running ebook-convert from the command line, it doesn't pause there nearly as long.

???

Is there something running as interpreted code that's compiled in the command line version? Or...???

Thanks...