View Single Post
Old 02-28-2014, 06:13 AM   #8
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by chaley View Post
We put it in this week.
That makes me feel better Though I didn't notice anything in changelog. But, I just found the commits with some comments.
Quote:
As for performance, of course YMMV depending on what you do but my experience when using the new DB methods is that the penalty is minimal. No syncing needed == nanoseconds. Syncing calibre to device probably incurs no penalty. Syncing device to calibre incurs only the calls to the DB methods to set calibre's data, which are fast.
Yes, I would expect any performance hit to be only noticeable with a lot of books on the device. When I have a play, I'll see.
davidfor is offline   Reply With Quote