Using Queuing Schemes on Routers For the most part, network devices have kept pace with evolving high-speed technology. Queuing schemes try to prevent low-volume applications, such as interactive web applications, from getting overtaken by large data transfers, typical of FTP traffic. Queuing, especially weighted fair queuing, doesn't work well for chunky flows because packets arriving in chunks tend to be discarded. Routers don't allow you to set guaranteed rates for specific traffic types. Rate specification in routers is imprecise.
Traffic classification is too coarse.
For example, router can't classify traffic by URL, treating all flows the same at the web site. Upgrading Web Servers Hardware improvements, server software, and HTTP protocols have caused the bottleneck to move away from the server, out to the access link. The PacketShaper Solution Traffic bottlenecks form at access links when a fast LAN pipe narrows into a slower WAN link, which causes multiple traffic sources to compete for limited capacity. This is where PacketShaper makes a difference. Imagine putting fine sand, rather than gravel, through a network pipe.