View Single Post
Old 10-11-2018, 08:51 PM   #9
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 Syana344 View Post
In the meantime I checked the calibre.metadata file. The size is 395MB.
Smaller than I thought. But, if you don't use many custom columns, it does keep the size down.

And what I should have asked is how big the database is. That is "KoboReader.sqlite" in the ".kobo" directory. Just a curiosity, but it must be getting past a GB.
Quote:
Ok, I have to precise that I use the ereader only to read... no games, no internet, no wifi. And of course, with this type of library, I take specially care of each single book - not corrupted, size, polish, classification, shelves etc - to avoid any corruption of the DB. On top, I have an full image to be able to restore the device if something breaks.

Thanks for the tip to turn off the "Read metadata from files on the device" feature. I'll try it out the next time I connect the device and have a look if it runs faster. (by the way, when I connected this evening, took exaclty 8mn45sec to synchronise with Calibre, which is already a good score for 53000 books on the device).
Yes, I'm surprised at it being so fast. And I'm not sure how much help turning the "Read metadata from files on the device" off will be. I just checked the code and it will only help if the book on the device hasn't previously been matched to the book in calibre. Or if the calibre.metadata file is missing.
Quote:
Regarding the FW version. In fact, I tried out the FW 3.19 but faced the issue that the device returned a "fatal error" around 40000 books. The only way out was a factory reset... and to start again. I have several GloHDs (not all mine, but I take care of) all set up in the same way, which excluded a HW issue on one single device. Therefore, I came to the conclusion, that the FW may be somehow limited.
That is something I hadn't heard of before. I can't think of what the changes in that time frame would have been that caused this. It isn't deliberate on Kobo's part, more likely something changed that used more memory. I'm curious about when it displayed the error. What was happening on the device.
Quote:
So this was a kind of no-go for me to upgrade.

Now, as I like to explore the limits of my devices , I'm making tests with the Clara... and the Clara is not compatible with the 3.18... so I must use a 4.x version. which I find "sexy". Just curious to see if I'll be able to cross the 40000, or if it's limited also.
One thing that has changed somewhere around version 4.3, is the speed of the collections list. Before this, if you had a lot of collections and any large collections, then it could take minutes to open the collection list. Afterwards, it was done to 10 seconds or so. There have been a lot of other performance improvements as well. Nothing as big as that, but generally it fells snappier. And a few of the other changes make me like the updates (series sorting, author list) but, I prefer the older tiled home screen.

Last edited by davidfor; 10-11-2018 at 08:59 PM. Reason: Added question about database size.
davidfor is offline   Reply With Quote