I have disabled all of my sync jobs but I find that the odrive process still consumes nearly a full core of CPU for reasons that are completely opaque. I have no idea what it is doing. It should be doing nothing. This has been going for nearly an hour since I stopped the sync AND restarted the process and it still pegs the CPU. What is going on?
I am running Mac OS 10.12.3.
I know you are working with a large volume of data, so it is likely that the elevated CPU you are seeing is the scanning process that happens on odrive start-up and periodically afterwards. When automatic sync is stopped nothing will be uploaded or downloaded automatically, but the scanning process will still run in the background, staying informed of changes being made and queueing them for later, if any are found.
I mentioned the large scale work we are currently devoting the bulk of our Engineering effort to in another thread. Resource efficiency, transparency, and general performance improvements are all part of this effort.
If you send a diagnostic from the odrive menu I can take a deeper look.
I will send one when the last sync has finished.