[chaley]

I am away with no access to my computers, so this is from memory.

Originally Posted by gsparks2

chaley,
Is this the expected behaviour of CC and Calibre?

Calibre Job times:
Start with 8940 books on device.
Upload 60 books to device 2m 44s
Send metadata to device 0m 19s
<disconnect CC>
<Wait ~30s until Calibre disconnects.>
<connect as Wireless Device in CC>
Get device information 0m 18s
Set library information 0m 1s
Get list of books on device 0m 43s
<during this time CC quickly sends metadata for the 60 books to Calibre, less than 10 seconds then Calibre analyses the books on device>

I would not expect CC to send any metadata at this time. It must send some base information to tell calibre what it needs to know to check its cache. If metadata for new books is being sent back to calibre then the last mod time in calibre's cache is being changed after the book is sent. How is a mystery. Do you have the reading list plugin installed with it keeping track of what is on the device? That would update metadata for the newly sent books at some point in the process.

Send metadata to device 2m 30s
<during this time CC displays progress bar for receiving metadata for the 60 books>
Total elapse time: ~6m 35s

This is consistent with the above: calibre and CC disagree about the metadata the cc has. Calibre must resend it.

It seems that metadata is sent several times back and forth. I am just trying to understand what is going on.

Thanks!

You can get a glorious amount of detail of you run calibre in debug mode. It will log the state of the cache, how many books are in it, how many are not, what it sends, and in many cases why.