@radovskyb As a solution for High CPU usage for polling large directories to monitor Create/Move events
watch.FilterOps(watcher.Create, watcher.Move)
We tried the following things:
But SetMaxEvents is not working as expected, as the files which are left after 5000 files are left as it is, once more files are created the watcher will again pickup random 5000 files to create events and the left over files are never picked up for event creation.
Would like to know if we misunderstood the use case for SetMaxEvents or using it in a wrong way
@radovskyb As a solution for High CPU usage for polling large directories to monitor Create/Move events
watch.FilterOps(watcher.Create, watcher.Move)We tried the following things:
increasing the polling duration (Observing high CPU Usage when watching on large directories. Expected? #24) (as we could avoid real time events notifications)
reducing the event per watch cycle by setting the max events
w.SetMaxEvents(5000)But SetMaxEvents is not working as expected, as the files which are left after 5000 files are left as it is, once more files are created the watcher will again pickup random 5000 files to create events and the left over files are never picked up for event creation.
Would like to know if we misunderstood the use case for SetMaxEvents or using it in a wrong way