On 30/08/2016 8:13 a.m., erdosain9 wrote: > Ok,thanks! > But something is wrong with my config............ > I dont have almost no users... (because is proxy testing) and i have too > many download avg. > > Look , this is Torch to the ip of proxy, to see whats going on... > > > <http://squid-web-proxy-cache.1019090.n4.nabble.com/file/n4679253/Captura_de_pantalla_de_2016-08-29_15-48-41.png> > Image does not exist. > <http://squid-web-proxy-cache.1019090.n4.nabble.com/file/n4679253/Captura_de_pantalla_de_2016-08-29_16-03-14.png> This appears to be showing several clients who are using only several KB/sec *download* which approximately match some of the delay pools download rates configured (~10-30 KBps). Also they are *uploading* very fast to the server. Delay pools controls download rates, not uploads. So that is as expected. Although not much upload data is expected when streaming _downloads_, so even if it did the 'burst' rates could account for most of the higher upload speeds. > > This is my config > > #Pools para ancho de Banda > delay_pools 5 > > ###VELOCIDAD PARA REDES SOCIALES > delay_class 1 1 > delay_parameters 1 10000/100000 > delay_access 1 allow redes_sociales limitado > delay_access 1 allow redes_sociales full > delay_access 1 allow redes_sociales adminis > > #Limitar YOUTUBE > delay_class 2 1 > delay_parameters 2 10000/100000 > delay_access 2 allow youtube adminis > delay_access 2 allow youtube full > delay_access 2 allow youtube limitado > > #Ancho de Banda Administracion > delay_class 3 2 > delay_parameters 3 512000/512000 60000/256000 > delay_access 3 allow adminis > > #Ancho de Banda Sistemas > delay_class 4 2 > delay_parameters 4 512000/512000 64000/256000 > delay_access 4 allow sistemas > > #Ancho de Banda Logistica > delay_class 5 2 > delay_parameters 5 256000/256000 30000/125000 > delay_access 5 allow limitado > > > if I have delay pools with low bandwidth . How can it be that "long period > of time " the squid has a bandwidth so high ?? 1) see above about download vs upload differences. 2) there are non-HTTP things involves with connections that use up bandwidth and being non-HTTP are not accounted by Squid - which can only account the HTTP message bytes. 3) you have both small and large bandwidth pools. Delay pools do not operate on connection or port basis. They operate on HTTP message bytes basis. So any given TCP connection may be rate limited one second (for one message) and then rate limited differently the next second (for its next message). Delay pools are a very old design from the days before QoS was properly standardized. It has many flaws. If you can do rate limiting with TOS / QoS controls it is recommended to use that instead. I hope to remove Delay Pools functionality from Squid as soon as the alternatives are able to meet all use-cases. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
