Select a network:
delay: 10ms, loss: 0.1%
delay: 200ms, loss: 2%
delay: 90ms, loss: 1%
delay: 150ms, loss: 2%
delay: 550ms, loss: 5%
Transfer Time by Bandwidth
Aspera's file transfer products are built on fasp file transport, an innovative reliable transfer protocol designed to meet the speed, bandwidth control, and security requirements of business-critical file transfer over any IP network (LAN, WAN, satellite, and wireless).
The results shown in this graph demonstrate that given a 150 Mb/s link capacity, fasp outperforms TCP regardless of packet loss or network delay. Under these conditions, TCP's best is still below 50 Mbps.
Unlike TCP throughput, fasp throughput is perfectly independent of network delay and robust to extreme packet loss. The bar graph below shows a comparison of throughput obtained by fasp versus the maximum throughput achievable for TCP-based file transfers on an OC-3 (155 Mbps) link under various latency and packet loss conditions. fasp transfer times are as fast as possible (up to 1,000x standard FTP) and highly predictable, regardless of network conditions. The maximum transfer speed is limited only by the resources (typically disk throughput) of the endpoint computers.
Delay and Loss Independent with Near-Zero Overhead. fasp uses standard UDP and achieves reliability in the application layer through a theoretically optimal approach that retransmits precisely the real packet loss on the channel. At 10% packet loss, fasp achieves 90% of the targeted throughput with less than 1% redundant data overhead.
Single Transport Stream. Unlike brute-force parallel TCP or similar protocols that divide a single file into constituent chunks and attempt to improve overall throughput through a parallel transmission, fasp achieves ideal efficiency with a single stream. In contrast, parallel TCP techniques exhaust system resources, don't work for small files, reduce speed on packet loss, and hog bandwidth from single stream flows.
Perfect Efficiency for Large Sets of Small Files. Using a novel file streamlining technique, fasp achieves the same ideal efficiency for transfers of large numbers of small files. For example, one thousand 2 MB files can be transmitted from the US to New Zealand with an effective transfer speed of 155 Mbps, filling an entire OC-3. As a result, fasp enables replication of large data sets, regardless of file sizes, at line speed on even the longest, fastest wide area networks.
Distance Neutral, Fast, Smooth Progressive Transfer. FASP supports progressive-style transfers where incoming data is processed during the transfer, such as feeding a media player. The transfer speed is maximum (for the earliest possible start of playback), and will not change with variable network conditions, in contrast to progressive download applications using HTTP that are slow to start playback, and may be plagued by glitches and interruptions due to congestion on the link.
Single FASP and TCP flows sharing a 10 Mbps bottleneck bandwidth (100 ms RTT). A FASP flow is started with a target rate at link capacity (9.95 Mbps) and runs steadily. After 120 seconds, a TCP flow starts up and stabilizes at 2.3 Mbps, TCP's self-limited rate. FASP detects the presence of TCP traffic and immediately reduces its own rate to use the remaining available bandwidth (7.7 Mbps), without inhibiting TCP. When FASP finishes two minutes later, TCP continues at about the same rate.
While fasp can fill any available bandwidth, fasp also includes an intelligent adaptive rate control mechanism that allows transfer rates to throttle down for precision fairness to standard TCP traffic, but automatically ramp up to fully utilize unused bandwidth (see Figures 1 and 2).
Automatic Adaptation to the Full, Available Bandwidth and Fair. The adaptive rate control algorithm is an original equation-based approach. When TCP's rate is self-limited on an uncongested link, fasp detects the unclaimed bandwidth and ramps up to fill it (Figure 1). When congestion builds up, fasp reduces rate to the TCP rate and equally shares the link with multiple TCP flows (Figure 2). This approach has fundamental benefits over the window-based flow control algorithm used by standard TCP and even new accelerated or "high-speed" TCP's:
Multiple FASP and TCP flows sharing a 2 Mbps bottleneck bandwidth (50 ms RTT). In this example a single FASP flow is started at the link capacity (1.97 Mbps). FASP 1 runs steadily at the target until the first TCP flow is started at two minutes. FASP 1 detects TCP 1 and immediately reduces rate to equally share the link at 1 Mbps. After two more minutes, a second TCP flow is started. Now FASP 1, TCP 1, and TCP 2 all equally share the link bandwidth at 660 kbps. Two minutes later, a second FASP flow starts up at a target of 1.97 Mbps. FASP 2 shoots up to the target but immediately detects the presence of the other flows and adjusts down as the other flows reapportion to equally share the link. Now all four flows are at 500 kbps. For the remainder of the test, one flow is terminated every two minutes. As each flow exits, the other flows reapportion the link bandwidth equally. The FASP flows zero in on the natural TCP rate at every interval, fairly sharing with TCP but with superior stability (less oscillation).
Configurable, Per-Flow Bandwidth Policies. The aggressiveness of any particular fasp flow relative to standard TCP or other fasp flows is configurable, and enables pre-set or user-defined bandwidth sharing policies such as equally fair and transparent background flows. For example, in Figure 2, two fasp flows configured to use a TCP-fair bandwidth policy share a 2 Mbps network with two standard TCP flows.
1) As the TCP flows enter, the fasp flows detect the congestion and
precisely divide the available bandwidth equally between one another,
and with TCP.
2) As the TCP flows exit, the fasp flows detect the newly available
bandwidth and immediately ramp up for full utilization.
Fast, precise, automatic discovery of the available bandwidth. Through state-of-the-art diagnostic algorithms, fasp is able to accurately discover the bottleneck link capacity (minimum capacity of all links) between any source and destination pair, within only a few seconds. This feature is not only useful for network profiling, but also allows for automatic configuration of the transfer rate, and maximum and minimum caps, as a percentage of the user's bandwidth capacity.