Quote:
Just as a teaser, the new db backend I am currently working on got the startup time for a 22K book library down from 11.5 seconds to 8.5 seconds on my machine.
|
That is good news as calibre spends most of its time in the db area.
For the record: catroot (& catroot2) seems to be
only involved in verifying driver signatures. For some reason that happened a lot during calibre startup.
However, catroot is not accessed anymore on my machine. And for the good part: I also do not encounter any freezes anymore

and calibre (depending on the selected database size) quickstarts now in seconds. Go figure
@BetterRed: Yes, i did (ages ago

)