A number of factors contribute to FileCatalyst’s fast file transfers. The most important of these is this:

FileCatalyst reaches full line speed.

FTP, HTTP, and other common technologies rely on a protocol called TCP. The very nature of TCP limits transfer
speed regardless of connection speed. This is true even under ideal network conditions, but becomes more apparent
as latency and packet loss increase.

By contrast, the FileCatalyst protocol is purpose-built for accelerated file transfer and
is immune to packet loss and latency. File transfer speed scales with available line speed, up to a full 10 Gbps, a top speed impossible to reach with conventional TCP-based solutions, and also three times faster than competing fast file transfer solutions.

The following tables show statistics from only a few of an infinite number of scenarios. The first is a common scenario; packet loss is intentionally low, revealing a best-case rather than worst-case scenario. The second table demonstrates the poor performance of FTP as link speed increases, while showcasing the ability of FileCatalyst to scale as an organization invests in a faster connection.

File Size: 10GB | Line Speed: 100 Mbps | Packet Loss: 0.1%

In this scenario, FileCatalyst reaches speeds from around 10–50 times faster than FTP depending on latency.

Latency (ms) FTP Transfer Time FileCatalyst Transfer Time
50 2 hr 25 min 14 min
100 8 hr 18 min 14 min
250 12 hr 15 min 14 min

Windows client to Linux server

File Size: 10GB | Line Speed: 10 Gbps | Packet Loss: 0.1%

In this scenario, the line speed has increased to 10 Gbps. FTP cannot even approach line speed, while FileCatalyst saturates the link.

Latency (ms) FTP Transfer Time FileCatalyst Transfer Time
50 40 min 13 sec
100 53 min 14 sec
250 67 min 14 sec

Linux client to Linux server