The main problem with deleting lots of files has to do with "Update Wait Time" (Advanced dialog). This controls how often a file or directory is synced with it's corresponding object in Atmos. When you tell Windows Explorer to delete a directory, the first thing it does is run down all the directories and count up how many files are to be deleted. This can cause GeoDrive to sync each directory to the cloud. If you Update Wait Time is very short, it is possible that after the files have been counted and now when it is actually deleting the files, it will sync all of those directories again.  You can try this:   I can check into enhancing Atmos Explorer so deletions are handled in the background for a future version.  When you delete lots of files, it is possible that the deletion on the local disk is faster than deleting the files in Atmos, so you may want to know when the files have been completely deleted in Atmos. This information is available in Performance Monitor:  Open Performance Monitor by clicking on the menu icon just to the left of the Home tab.  Add the following counter:   The Change Log queue is where deletion requests get queued. When that queue is empty, all of the deletions are complete. There are other counters associated with the Changelog to show more detailed information.
Using GeoDrive for Windows it is very difficult to delete previously uploaded files from it. Using Windows Explorer the Preparing to Delete phase takes a very long time which must be followed by the actual deletion which also takes forever when it works. Often there are files Windows does not allow you to delete. Using the Atmos Explorer from within GeoDrive UI is equally as slow and goes into a Not Responding mode forever as well.  Is the above expected behavior? Is there a better more efficient way to delete uploaded files from a GeoDrive?
How can I delete many files that have been uploaded via GeoDrive