You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.
I'm running on Windows and I recently started using this on a directory tree that contains almost 500,000 files and the Listen module that this uses takes a good chunk of time to pre-process and index the directory tree before it actually starts listening. The gatling-rsync plugin works great for tracking/monitoring changes because it uses more OS native methods of tracking files. If the listening method of that plugin were combined with the 'only-changed' functionality of this plugin, it would make this thing AWESOME for working on any size directory.
The text was updated successfully, but these errors were encountered:
Pardon my ignorance, as I didn't dig close enough into the Listen code to see that on windows it already uses native means of tracking changes. Perhaps it pegs the CPU because of the indexing of so many files? I'm not sure.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm running on Windows and I recently started using this on a directory tree that contains almost 500,000 files and the Listen module that this uses takes a good chunk of time to pre-process and index the directory tree before it actually starts listening. The gatling-rsync plugin works great for tracking/monitoring changes because it uses more OS native methods of tracking files. If the listening method of that plugin were combined with the 'only-changed' functionality of this plugin, it would make this thing AWESOME for working on any size directory.
The text was updated successfully, but these errors were encountered: