Thread: Large Database Issues
View Single Post
Old 07-24-2011, 10:22 AM   #4
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 29,809
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by phil_ga View Post


I hugely appreciate everything done to make this program the joy it currently is, but these two issues are really highly limiting (large db size, and the high risk of dependence on a single file that gets easily corrupted). I am hoping I am simply wrong and there is already a solution out there? Please?
Like Walt, crashes are few and far between and have been limited to specific releases.
Calibre conversions can stress marginal PC hardware. If you edit metadata with a background conversion running, it is possible that you PSU or cooling fans/dirty fins may not keep up with the load.

Mains power quality is suffering. Use of a UPS model with AVR is highly suggested.

As to DB size. I believe that running the maintenance checks might 'pack' the DB as a side effect.
Last edited by theducks; 07-24-2011 at 10:24 AM.
theducks is online now   Reply With Quote