The second template creates a folder per first-author then stores the book (a two-level hierarchy). The first template stores all the books in one folder, using no sub-folders (a one-level hierarchy). Each experiment uses a different CC file template.
We ran three experiment to illustrate the problem/solution. See How do I get the same file names in CC no matter which connection I use? for more information.
We recommend using CC's file template system instead of changing the template in calibre, especially if you use the Content Server or Cloud connections. You can do this by using a file save template that limits the number of entries in any one directory. Regardless of the cause, limiting the number of entries in any given directory will help avoid this slowdown. For example, if there are 3,000 books in a directory, doing the check will run 3,000 times slower than when the library was empty.Ī similar situation can arise with main memory for a few reasons, such as the implementation of the Android Storage Access Framework on the device being less than optimal, the device using a linear lookup file system for main memory, or the device file name cache being too small. Clearly the more files in the directory the slower Android will run. The file is (almost) never there, so the time required is the worst case: a search of all the files in the directory. position) in order to see if the file is already there. Directories (folders) in FAT32 are not indexed, so whenever CC creates a file the operating system (Android) must do a linear search (1st, 2nd, 3rd, 4th. SD cards usually use a FAT32 file system.
The most common is triggered by putting books on an SD Card, but it can also happen with books in main memory. In some situations creating new files on an Android device can become very slow.
0 kommentar(er)
