One of the big ideas behind odrive’s sync engine is the idea of “progressive” sync, where you can get to and sync the specific data you need at that time without having to sync down the entirety of your remote data.
The most difficult use cases to make really smooth are those dealing with bulk operations, like bulk downloading, especially against sprawling structures, as mentioned above. You’ll see these, for example, in software like Adobe Lightroom, Apple Photos, and Scrivener.
These are typical in photo and video editing type of software, where they tend to have these ridiculously complex data structures with thousands and thousands of folders. Hi for the information! Everyone’s data is different and you look to have a lot of what we call “sprawling” folder structures. Let me know if you notice any changes in behavior after doing this.
Once the tray menu is up, go to the top item in the menu (it will say “Ready to sync new changes” or “Syncing changes”) and select “Disable background scanning”. This will disable odrive’s monitoring of the local filesystem events, which can get pretty noisy during bulk download operations. Change "disableFSEvents": false, to "disableFSEvents": true, and then save the file. Double-click to open the “odrive_user_general_conf.txt” in the root of your odrive folder. This will reduce the overhead and should allow for smoother operation. If your current goal is bulk download of your remote data, we can try to scope the amount of work odrive is doing to just that, until it is done. I took a look at the diagnostic and there is a lot of activity happening, which can spike the CPU.Ĭan you walk me through the actions you are currently taking with odrive? Are you attempting to download everything in your Google Drive to your local system?
0 kommentar(er)
