Article was started here
However this comment system will not let me make more than 3 replies so read the above post first and then come here.
(By the way continued no response from anybody at Insync, a little disappointing)
See other experiments I made in this thread.
So with the 120 GB or so of information loaded into the Google drive area g:\gdrive sucessfully loaded using the free Google client it was now time to see what Insync can do.
I stopped the Google Client
At this point local machine and remote host have about 120GB of identical data
Insync is started normally and needs to scan for changes and then presumably just needs to check the 200,000 files are exactly the same between local and Google cloud.
20151103 13:22 Insync started
20151103 18:49 Insync finishes scanning changes decided 282K items to queue
20151103 20:49 Now 275K items
20151104 07:07 222K items queued
20151104 09:24 211 Items queued
20151104 17:49 150K items queued
20151104 20:13 163K items queued. WAIT A MINUTE. THE NUMBER GOT LARGER AND THERE
HAS BEEN NO ACTIVITY ON LOCAL OR HOST! WHAT'S GOING ON
20151104 21:24 166K items. It is STILL INCREASING!!
Current position is therefore
- Insysnc started with 282K items. In 24 hours it got it down to 163K or so, with the anomoly that somewhere it decided there were more items to synchronise.
- Clearly it is several magnitude orders slower than the native google client which pushed everything in less than 20 hours.
It would be a good debug tool if the the verbosity of the Progress dialog could be set to more or less to aid comprehension.