Quote:
Originally Posted by BetterRed
@ aurne - I believe one reason will be that the 'database' on which desktop calibre operates is not the on-disk metadata.db sqlite database as such. Instead it operates on an in-memory 'database' which is initially built from the on-disk sqlite metadata.db when calibre starts. See API documentation for the database interface
BR |
Thanks! That's pretty informative, though it seems like a really non-standard way to handle databases. The wiki quotes "maximum performance" as justification. Do you, or anyone else have any numbers regarding the performance differential between in-memory and traditional sqlite?
Anyways, it seems like my original architecture of a single server performing db IO with multiple clients connected will be the best choice going forward.