[gwbas1c]

I find this very strange, as the major file synchronization client that I work on doesn't have this problem. We use the fsevents API, and it's pretty localized to the folders we monitor.

(I will admit that we have performance issues when users sync more than 100,000 files; but that's more due to fundamental limits of what you can do in a user-mode application.)

Perhaps Dropbox is just trying to trap deleting / moving / renaming the Dropbox folder? That's something that's tricky to do; and we had to disable our technique to do it because it had too many side effects.

[zw]

Based on the warnings in the Console log back when I used Dropbox, Dropbox isn't using fsevents API appropriately but is instead reading from the raw fsevents firehose.