Reviewing Packet Shaping Products

Comments

The original posting of this website contained the following paragraph, recommended for insertion in the document by our Packeteer engineer:

Packeteer

"During ALL tests Rate Policies on the PacketShaper were NOT tested. This technology is where Packeteer has most of its patents and what typically provides the largest differentiation between the PacketShaper and all other QoS technologies. It is also the shaping that most higher education institutions rely on to shape their P2P applications, specifically in the inbound direction where queuing is fairly ineffective. The Allot uses queuing and queuing can't effect packets until they get to the device. In which case the NetEnforcer's shaping doesn't affect inbound packets until they have already crossed the WAN, where as rate shaping policies (not tested mind you) keep the packets off the network until needed, thus removing most queues & latency from the network. Other items not even considered were classification (which again is typically a strong feature for the PacketShaper, particularly in P2P traffic types) and application monitoring (NetEnforcer only tracks bps, bytes and packets it drops from its queues and per-flow data where as the PacketShaper tracks over 55 performance metrics with many of them very focused on health not just throughput)."

At the same time, the introduction page has been edited to indicate only factual issues raised by Packeteer.