Quote:
Originally Posted by GeoffR
Check the save template in the KoboTouch plugin, a reset and reload is the ideal time if you want to make a change. The default template will result in very long pathnames, and create one directory per author. FAT filesystems have limits on the number of files per directory, and long filenames reduce the number of files that can fit. Every extra 11 characters in the filename counts as one extra file towards the limit. Cover and thumbnail images, annotations files, etc. are created using the same base filename so they will be very long too. Also in some situations having lots of files (or subdirectories) in one directory can slow down access, so idealy you want the filenames to be as short as possible, but not result in too many files (or subdirectories) per directory. The template must generate unique names though, so you need to allow for books by different authors with the same title. I don't really know how much effect this has on performance since I don't have a control device to compare with, maybe none, but it can't hurt.
|
That's not quite right. The device uses FAT32 and the limitation is per directory. Hence, a few subdirectories will minimise the issues caused by long filenames. For the cover images, the firmware subdivides those into a directory tree, so there is no problem there so long as the generated path isn't to long. The driver in calibre should be managing that.
Quote:
Originally Posted by DandalfTheWhite
meeera:
Thanks for the reply. I took out the sd card and restarted the kobo and it still took forever to be functional. I added a few books to the main memory including the one that didn't work as well as one I just read on it and know works. The good one worked and the bad one still didn't. With five books on the kobo restarting still took ages.
|
With the full database, removing the SD card wouldn't necessarily help. The database entries for the books on the card are still in the database. That means any database operation would still have to take that into account. But, it might help some operations as a lot of information is cached. If the firmware is smart, if the SD card is not there, it might only load information into the cache for the books it still sees.
[/QUOTE]
I logged out and it restarted as soon as I did that. Had to go through setup again and redo my wifi and all that. After it got back to the home screen it seemed a lot faster. The broken book even opened, so maybe it wasn't broken after all. Will still use epub check to make sure it's alright.
It is processing now, will take all night probably. Will update in the morning. Thanks again for your help!
[/QUOTE]
From the first post, I think the main issue is the total number of books. At about 2600 books, I don't see any real performance problems. It is probably slower than when I had about 200, but not enough for me to worry about. I did wonder if there was some database corruption. The long startup time might have been the device attempting to fix this, or hitting problems when it tried to access parts of the database. But, I doubt if a factory reset would help. The logout and back in generates a new clean database and hopefully that will solve it.
One thing I normally suggest in these circumstances is to take a backup before the logout or factory reset. I take a full backup of the user partition of the device. That way if the logout or factory reset doesn't help, I can restore everything and get back to were I was.
I will be interested to know if this helps. I'm also curious about how long it takes to process all the books. The processing is a lot faster than some of the the earlier firmware, but it's going to take a while. Maybe we should start a book. I'll take 10 hours.