What is the expected reduction in throughput when using a web proxy instead of the DPI engine?

When utilizing a web proxy as opposed to the Deep Packet Inspection (DPI) engine, the expected reduction in throughput is generally around 25%. This reduction primarily occurs due to the additional overhead involved in processing web traffic through the proxy. The web proxy must inspect, filter, and potentially cache requests and responses, which can introduce delays.

In contrast, the DPI engine is designed for high-performance inspection of content within the traffic stream without the need to re-route data, allowing for the processing of packets at high speeds. While both methods aim to secure and manage web traffic, the way they handle data can lead to varying levels of efficiency. The web proxy’s operations can create bottlenecks, impacting throughput to a noticeable degree, hence the projected reduction of up to 25% when compared to the more streamlined DPI engine.