MobileRead Forums - View Single Post - Transfer of files on Android is incredibly slow, but same files super quick on iPad?

chaley · 01-24-2018, 06:35 AM

Also, if the info in that FAQ doesn't apply to you, we can get some diagnostic information from a CC debug log. For example, I sent a book to my test device and the debug log contains the following:

Code:

2018-01-24 12:07:59.493:  calibre sent command SEND_BOOK
2018-01-24 12:07:59.495:  current lpath=History of Don Quixote ...
2018-01-24 12:07:59.496:  Command SendBook: receiving sequence 0 of 1, title=The History of ...
2018-01-24 12:08:02.281:  Command SendBook: received book. length=8778128
2018-01-24 12:08:02.283:  Command SendBook: creating queue object
2018-01-24 12:08:02.285:  DbUpdateThread starting: command=SendBook, supportsSync=true, allowCreation=true
2018-01-24 12:08:02.287:  Command SendBook: queued metadata write. queue length=0
2018-01-24 12:08:02.684:  Command SendBook: queue finished 0 in 403 ms, title=The History of Don Quixote, Volume 1, Complete, lpath=History of Don Quixote, Volume 1, Complete, The - Miguel de Cervantes Raavedra (1235).epub
2018-01-24 12:08:02.685:  Command SendBook: queue thread exited

We see that it took almost 3 seconds to receive an 8 megabyte book. The time to create the file is included here. It took 403 milliseconds to add the book to CC's database.

The CC receive book progress bar can give you some information without referring to a debug log:

The bar won't move until the file is created. If the time is spent here then the FAQ should be relevant.
The bar will move while the book is being received over the network. If the time is spent here then the network on the device is very slow.
The bar will sit at the end while writing CC's database. If the time is here then updating the CC database is slow. CC "Settings / Other / Clean book database" might help.

01-24-2018, 06:35 AM	#3
chaley Grand Sorcerer Posts: 12,495 Karma: 8065348 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	Also, if the info in that FAQ doesn't apply to you, we can get some diagnostic information from a CC debug log. For example, I sent a book to my test device and the debug log contains the following: Code: 2018-01-24 12:07:59.493: calibre sent command SEND_BOOK 2018-01-24 12:07:59.495: current lpath=History of Don Quixote ... 2018-01-24 12:07:59.496: Command SendBook: receiving sequence 0 of 1, title=The History of ... 2018-01-24 12:08:02.281: Command SendBook: received book. length=8778128 2018-01-24 12:08:02.283: Command SendBook: creating queue object 2018-01-24 12:08:02.285: DbUpdateThread starting: command=SendBook, supportsSync=true, allowCreation=true 2018-01-24 12:08:02.287: Command SendBook: queued metadata write. queue length=0 2018-01-24 12:08:02.684: Command SendBook: queue finished 0 in 403 ms, title=The History of Don Quixote, Volume 1, Complete, lpath=History of Don Quixote, Volume 1, Complete, The - Miguel de Cervantes Raavedra (1235).epub 2018-01-24 12:08:02.685: Command SendBook: queue thread exited We see that it took almost 3 seconds to receive an 8 megabyte book. The time to create the file is included here. It took 403 milliseconds to add the book to CC's database. The CC receive book progress bar can give you some information without referring to a debug log: The bar won't move until the file is created. If the time is spent here then the FAQ should be relevant. The bar will move while the book is being received over the network. If the time is spent here then the network on the device is very slow. The bar will sit at the end while writing CC's database. If the time is here then updating the CC database is slow. CC "Settings / Other / Clean book database" might help.