[SLL] mod_throttle?

[Bill Warner]

Thanks for the replies. So far I've only added a traffic shaper that 
gives port 22 hi priority. That, however, won't be sufficient, as my 
original idea was to assign distinct bandwidths (or better, priorities) 
to different web content. That logic is implemented in mod_throttle, but 
unfortunately I'm running apache2. I downloaded and but have not yet 
installed mod_bwshare. AFICT, it's simpler in that it applies a 
heuristic to identify clients that are using too much bandwidth. That 
might be better than assigning limits to particular content, in that it 
won't need maintanance as content changes, so I'm hopeful.

Paul wrote:

>I've not tried mod_throttle because I believe it doesn't work
>with apache2, and I haven't tried mod_bwshare that Glenn
>suggested.
>
>One other way to do it is via QoS at the TCP level.
>For example, this snippet hard throttles my bandwidth
>(all traffic, not just http) to 40Mbps:
>
># tc qdisc add dev eth0 root tbf rate 40Mbit latency 50ms burst 50Kb
>
># tc qdisc show
># tc -s -d qdisc ls
>  
>