Performance
SFTP throughput depends on network latency, buffer size, concurrency, and the storage being accessed. The shared transfer-speed principles explain why available bandwidth alone does not determine the rate. If your workflow does not require SFTP, consider the preferred apps, which provide transfer optimizations through HTTPS.
When a partner or application requires SFTP, use the settings below to tune that connection.
Maximize the Buffer Size (Data Chunk Size) in Your SFTP Client
Most SFTP clients send data in chunks of 32 kilobytes.
We recommend increasing this size by 4-32x in your client. Larger chunks can carry more data in each SFTP request, reducing the number of requests needed to transfer a large file. Chunk size and the number of outstanding requests together set a client-side limit on data in flight.
The improvement depends on how your client handles requests, network latency, and the server's supported request size, so measure the same transfer as you adjust the setting. Other protocols handle this process much more automatically.
If you are using the command line sftp tool, you can set the buffer size using the -B option: sftp -B 128000 username@MYCOMPANY.files.com
If you are using any other client, look for settings related to buffer size or data chunk size and increase them gradually while measuring throughput.
Use Many Parallel Connections
Follow the shared parallel-connection recommendation, including the combined limit for apps sharing one source IP address. The client settings below start with 10 simultaneous transfers.
Password-based two-factor authentication narrows this. Parallel connections and later reconnects can reuse the same password and code from the same source IP address to the same Files.com server address. Reuse ends at the expiration assigned to the first sign-in, or earlier if that sign-in is invalidated; another connection does not restart the period. A connection that reaches a different server needs a fresh code even before then. Authenticate unattended transfers with a key instead. Files.com native apps complete the second factor at login and retain parallel transfers.
To increase the number of simultaneous connections in FileZilla, go to Edit > Settings > Transfers and increase the Maximum simultaneous transfers setting to 10.
In Cyberduck, open Preferences > Transfers and set Transfer Files to Open multiple connections.
Then open the Transfers window and set the connection limit to 10. The control is in the lower right on Windows and in the toolbar on macOS. Cyberduck's connection settings apply to parallel file transfers and segmented downloads; keep any increase within the shared limit above.
Increasing the number of simultaneous connections will help when uploading multiple files at the same time but will not have any effect when uploading a single file.
Minimize Network Latency
Network latency is measured as the round-trip delay between sending data across a network and receiving a reply that the data was received. Higher latency, also known as "lag", can be caused by:
- physical limitations, such as your physical network connection.
- how much data is currently saturating your network connection.
- the network distance between you and your destination.
- network tools and software that regulate or restrict bandwidth usage.
Network latency has a large impact on SFTP performance. Whenever possible, use the best physical network available to you and achieve the shortest network distance possible.
Use the Best Physical Network Available to You
Choose a physical ethernet connection over a Wi-Fi connection.
Use the Shortest Network Distance Possible
Connect from the same geographic region as the destination. Using VPNs or network proxies located in other geographic regions always adds latency.
For example, if you are located in the EU and the SFTP destination is also located in the EU, but your VPN is located in the US, all your data will be routed through the US. That causes much higher latency despite the SFTP destination being geographically close to you.
Multi-Region or Remote Server Mount Considerations
Files.com supports accessing files stored in multiple regions or on multiple remote servers from one unified SFTP connection. Accessing these locations through one SFTP connection also creates performance challenges.
When accessing files in multiple regions or on multiple remote servers from one single connection, we recommend switching to a Files.com CLI, SDK, or Desktop app, which are optimized for multi-region scenarios.
Custom Domain Considerations
If you are using a custom domain with Files.com, note that custom domains are always hosted in a single region. If you are not physically located near the region where your custom domain is hosted, SFTP performance will be very poor.
We recommend testing connections to app.files.com rather than your custom domain if you are trying to use SFTP from a region other than the one where the domain is hosted. That can increase SFTP performance by reducing network latency dramatically.
The app.files.com domain is available in many different geographies. app.files.com is not available if your Files.com site uses a Custom username namespace or has disabled global acceleration features.
Performance is worse still when a Files.com site's custom domain is in one region, you are accessing files located in another region, and your SFTP client is in a third region. In cross-region cases like that, we recommend switching to a Files.com CLI, SDK, or Desktop app, which are optimized for multi-region scenarios.