Quote:
Originally Posted by chaley
I will fix this by not permitting the queue to get longer than X, probably 4 or 5. If it gets that long, CC will wait for a book to get to the database before it adds another to the queue. This will slow down the apparent network transfer speed, but will ensure that when the transfers finish there isn't minutes of work left to do.
|
Seems reasonable to me since loading the books is a one time thing.
The one thing that bugs me is on the calibre side, it took
40 minutes for the 9800 book job to enter the queue then 45 more minutes before the books started to transfer. But again since it is a one time thing it isn't a problem.
Update:It turns out the slow time mentioned above was due to disk intensive jobs I was running at the same time. The actual time is a more acceptable 15 minutes for the 9800 book job to enter the queue then 20 more minutes before the books started to transfer.
Quote:
Originally Posted by chaley
@DoctorOhh, this will restore the network slowdown you previously saw, but I hope to a lesser degree.
|
The network slowdown I noticed was during the uploading of the metadata from my device to calibre. Something you did smoothed out the metadata upload in this build.
Quote:
Originally Posted by chaley
Regarding the bug in the cleaning progress dialog: thanks. I have fixed that.
|
Glad I could stumble over something that could help. I say stumble because the tablet slipped out of my hand and I noticed the results.
Quote:
Originally Posted by chaley
Regarding the speedup in grouping: this must be "caused" by the database clean because I made no changes in that code. The cleaning process creates a new database with everything packed together in a nice order and all empty space released. My guess (close to a certainty) is that the "nice order" is permitting the database queries to run substantially faster, giving you the performance improvement.
|
It was already fast that's why I said subjectively it seemed faster.
Quote:
Originally Posted by chaley
Finally, I am adding the ability for CC to write its own debug log. There will be a preference that when checked causes CC to log *lots of stuff* to the file calibre.companion.debug.log.txt in the root folder of the device public storage. It is there because where logging happens I cannot get any application-specific configuration, so I can't put the file into CC's default books folder. Oh well...
|
Sounds valuable for future optimization.