> > Wojciech Milc wrote:
> > > But there is one question: how to set configuration to prevent
> > > ALL traffic (summary of pool A and pool B) to be higher than 512?
> > > Both pools together have 768 kbps and as I understand THIS will be
> > > maximum total bandwith eaten up by squid? How to limit a TOTAL
> > > bandwidth to 512 kbps and preferably set a priority, say
> to pool A?
> >
> > Squid doesn't currently support that.
>
> THAT = priority table or THAT = total bandwitdh level?
Either. Priority of all sessions is equal, with randomization to
prevent starvation. The bandwidth level can be controlled by
class 1, class 2 or class 3, however each traffic flow is only
considered in one delay pool (in a class 3, it's actually three
"pools", but each from the one configuration line).
> Anyway, if I there would be two class 1 pools set at 512 kbps
> and 768 kbps and the throughput on the WAN interface would be
> limited to 1024 kbps total, nevermind how (by a DSL modem
> speed or CBQ or the other way) is there a way to set a priorities
> between a pools?
Limiting in that way is throwing away traffic - squid delay pools
attempt to slow down the TCP connection rather than discarding traffic.
Probably not much real difference though :)
But no, as above, there's no connection prioritization support.
David.
Received on Mon Mar 18 2002 - 18:11:48 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:06:59 MST