Quote:
Originally Posted by Pierre-Olivier
I was too much enthusiast... 
As the number of books increase, the transfer rate is going lower and lower.
52minutes needed to transfer 683 books.
I'm afraid of the future, since I've only transferred 4559 books ... |
What this means is that you have a lot of books where the authors have the same first letter, or even worse that you have a lot of books by the same author. The SPF begins to slow down if there are more than around 300 files/folders in a given folder. There is nothing that CC can do to prevent this.
What is needed is to find some metadata that ensures that the books are distributed through folders so that no folder has more than a few hundred folders/files in it. It appears that in your case using the first author doesn't achieve that goal. I am guessing with my suggestions because only you know what is in your library. That said, changing the template to
Code:
{uuid:%2.2s}/{title}
will introduce a lot of randomness. The uuid is (pseudo-)random so that should split the top level into 256 folders (the uuid is in hex, base 16). Assuming a perfect distribution (perhaps a bad assumption) this template will create 256 folders each containing around 100 books. Of course, using the uuid means that the path names are useless for browsing with a file manager, but that really shouldn't matter.
If you want even more separation then perhaps use
Code:
{uuid:%2.2s}/{first_author:%1.1s}/{title}
Quote:
|
May I suggest one thing ? Since I faced the problem because I changed my smartphone, but keep the same SD card : Wouldn't it be possible for you to add a saving capability for the Data base (different from the Library) ? For example, someone, like me, want to change his phone but continuing using the same SD card . On the old phone, CC will save the data base on the SD card, then install CC on the new phone (with old SD Card), and import the data base and that's all, Books are in the same place ...
|
How does this differ from the existing backup & recovery mechanism? You can save the database and settings then reload them on the new device.
You are assuming that the new version of android would permit reading the old SD card folders, something that is not guaranteed. It is common for the new version to require re-initializing the SD card.