Hi, thanks Amos for always share your knowledge. "No there is 500KB/sec allocated to client response (download) traffic on "first-come basis. "This is effectively the same configuration as kernel routing QoS "controls allowing the Squid process to access 500KB/s of traffic inbound "for servers and unlimited upload traffic to servers. Here squid decide what we can share to each connection, the first machine get full bucket, if other machine arrive squid decide what he can receive from the bucket and continue the same to others users? Until they eat all the bucket and fill again the bucket to share? example 2: delay_pool_count 1 delay_class 1 3 delay_parameters 1 500000/562500 -1/-1 4000/4000 delay_initial_bucket_level 100 Start will full bucket, here we have one bucket of 500kb/s burst 562kb/s for all my clients but each on my clients will get <= 32kb/s(max 32kb/s) from their single bucket? About the QoS, is what I'm trying to manage, but I had been testing squid delay-pools and they help in some manner controlling users appetite. QoS trying to see how to integrate with squid, because once squid start controlling inbound is came of difficult to me because 80/443 are only seen by single client(squid), QoS won't see my lan connections to those ports which are who eat my bandwidth, but working on. On Thu, Mar 20, 2014 at 9:48 PM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > On 21/03/2014 6:04 a.m., Beto Moreno wrote: >> Hi. >> >> Squid 3.1.22. >> >> Learning this feature from squid, delay-pools. >> >> 1; aggregate the most simple. >> -If I have a dsl 6Mb/s but I want to share to my users 4MB/s and the >> rest for my other servers. >> >> delay_pool_count 1 >> delay_class 1 1 >> delay_parameters 1 500000/562500 ==> 4.5Mb/s Max and hold this to 4Mb/s. >> delay_initial_bucket_level 100 <=== I want to start with full 4.5MB right? >> >> Once my clients start surfing, example 10 users, squid will share >> 500000/10 they will have >> +/- 50Kb/s each one? > > No there is 500KB/sec allocated to client response (download) traffic on > first-come basis. > > This is effectively the same configuration as kernel routing QoS > controls allowing the Squid process to access 500KB/s of traffic inbound > for servers and unlimited upload traffic to servers. > > PS. the delay pools feature in Squid predates QoS and most traffic > management is now far better done by QoS tools instead of Squid delay pools. > > >> >> My network is class C. >> >> If more clients arrive they will again do some calculations >> rate/numbers of users? >> >> Exist a way to see the status of the pools connections example with cachemgr? > > Delay pools should be listed in the "delay" report. > > Amos >
