|
Yeah, it was always "slower" but never realized *HOW* slow... For comparison, after using ENV VAR to point global Library DB to local drive, doing FFF metadata update from stored metadata column on 5000 books took ~50 mins? vs prev 2000 books in 20hours... Guessing Calibre might do something with file locking workaround, like try to file lock, if you can't, sleep XX seconds and verify nothing changed then go ahead and do something... This could explain Calibre just "hanging" with no network, disk or CPU usage when DB is on NAS. It was "tolerable" when updating handfuls of books, but adding a new Column that must be populated from stored metadata did a *lot* of DB access, so the problem was no longer "tolerable"...
I have not tried changing Libraries yet, but I did load up Calibre without the ENV var and it loaded with an empty DB (NAS copy is renamed as a backup) but closing, removing empty DB file and setting ENV had things working again... just annoying... Would be nice if Calibre could do a pointer or something for DB setting, so you could have a minimal DB file wherever and store a setting for pointing to "real" DB somewhere else... again, not a FFF issue at all but something users might run across...
|