Persistent remote directory cache for synchronization when remote side is known to be unchanged
Hello,
I would like to request an optional feature to improve synchronization performance for cases where the remote side is effectively immutable.
Use case:
I synchronize a local folder against a remote FTP directory containing around 10,000+ files. In my workflow, the remote files never change. Only the local side changes. However, each synchronization run still re-reads and re-analyzes the full remote directory listing, which adds significant overhead.
Requested feature:
An option to persist and reuse the last known remote directory state between sessions, so WinSCP does not need to fully rescan the remote side on every sync.
Possible forms this could take:
- Persistent remote directory cache across sessions
- "Assume remote side unchanged" option for synchronization
- Manual "trust previous remote scan" mode
- Revalidate remote state only when explicitly requested by the user
Expected benefit:
This would greatly speed up repeated synchronization jobs for large remote directories where the server content is known to be stable.
Important note:
I understand this would need to be optional, because it is not safe for general use. But for controlled workflows, it could save a lot of time and unnecessary directory listing operations.
Thank you.
I would like to request an optional feature to improve synchronization performance for cases where the remote side is effectively immutable.
Use case:
I synchronize a local folder against a remote FTP directory containing around 10,000+ files. In my workflow, the remote files never change. Only the local side changes. However, each synchronization run still re-reads and re-analyzes the full remote directory listing, which adds significant overhead.
Requested feature:
An option to persist and reuse the last known remote directory state between sessions, so WinSCP does not need to fully rescan the remote side on every sync.
Possible forms this could take:
- Persistent remote directory cache across sessions
- "Assume remote side unchanged" option for synchronization
- Manual "trust previous remote scan" mode
- Revalidate remote state only when explicitly requested by the user
Expected benefit:
This would greatly speed up repeated synchronization jobs for large remote directories where the server content is known to be stable.
Important note:
I understand this would need to be optional, because it is not safe for general use. But for controlled workflows, it could save a lot of time and unnecessary directory listing operations.
Thank you.