TCP is used by the majority of corporate SW applications. Howver, TCP tends to deliver slower speeds than what the underlying network supports (both in classical WANs and in SD-WANs), especially when different corporate branches are located far apart, or when WiFi is used for user access. The Bequant TCP Acceleration (BTA) significantly improves the performance of TCP traffic in these WAN networks, delivering an improved user experience and enhancing critical enterprise applications. These improvements are obtained at a cost that is an order of magnitude below that of application-based optimizers. In addition, TCP-level optimization is done without breaking end to end encryption, so the security of valuable data and applications is not compromised, and optimization is not dependent on proprietary application changes.
This section shows the acceleration obtained in an Enterprise with both Wifi and Ethenet users, and with a centralized fiber Internet access. The results are broken down by Internet services, with Microsoft also including internal Microsoft applications. A small percentage of TCP connections are randomly left without optimization, with the performance of each individual TCP transfer being registered, and the optimized results are compared with the non-optimized ones to obtain the acceleration percentage (the increase in average speed). Uplink or downlink direction is from the point of view of the Bequant device deployed in the centralized headquarters, so downloads of contents residing in the headquarters servers perfomed from remote branches are taken as uplink traffic.
The Bequant software can run on a single Bequant Node (BQN), transparently deployed at the central data center as a bump-in-the-wire in front of corporate servers and the Internet access. This deployment provides an important economic advantage, because only one Bequant device is required, and is advisable when there are large data flows from a centralized enterprise data center to the branches and when there is a centralized Internet access at the headquarters location.
While a one-ended deployment (with the BQN in one centralized data center) offers important economic advantages, two-ended deployments (with the BQN in multiple branches) delivers improved performance.