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 May 29, 2020. It is now read-only.
The awssyncer will inherently need to do a full synchronisation every couple of hours. The reason for this is that inotify may easily miss events in our case. For example, in case files are hardlinked, we'll only receive a single event for one of the paths.
Still, there is room for improving the number of requests we send over to S3. If we would cache the state of S3 across calls, we'd know exactly what to sync and what can be skipped.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The awssyncer will inherently need to do a full synchronisation every couple of hours. The reason for this is that inotify may easily miss events in our case. For example, in case files are hardlinked, we'll only receive a single event for one of the paths.
Still, there is room for improving the number of requests we send over to S3. If we would cache the state of S3 across calls, we'd know exactly what to sync and what can be skipped.
The text was updated successfully, but these errors were encountered: