How it Compares

RocketStream can’t increase the size of your data pipe, but it does make sure you fill it. When networks experience latency, either due to router hops, congestion, or just because of geographic distances, TCP slows down the transfer of data. This can drastically reduce throughput, even when nothing is wrong.

For example, when sending data from Los Angeles to New York, network latency limits TCP throughput to around 4 Mb/s, regardless of the bandwidth available. But RocketStream can overcome this and let you fill your entire data pipe, so if you have a DS-3, Fast Ethernet, or OC-3 connection, you finally get what you paid for.

The graph above shows how FTP performance falls off as ping times between source and destination get larger across a 100 Mb/s pipe. In this example, RocketStream beats FTP by a factor of 137x at very long distances.

If the available bandwidth had been even higher, like an OC-3 or OC-12, RocketStream would have performed even better, but FTP would have remained just as sluggish.

Not everyone is lucky enough to have such large IP connections. What about more modest pipe sizes? RocketStream can still help. For example, a 10 Mb/s connection is still large enough to experience significant impairment from network latency, as shown in the graph below. For ping times less than 300 ms, throughput can be maximized by selecting RocketStream’s new PDP protocol, while over very long distances or congested networks, RocketStream’s powerful variation of UDP maximizes the pipe.

Of course, maximizing bandwidth is just one of the benefits of RocketStream. Users get all this, plus the security and reliability built into the RocketStream protocol. Pro users also get a powerful set of automation features, like synchronization, hot folders, and job scheduling. All of these functions together now make RocketStreaming your data simple, painless, and extremely fast.