Sent in private to Amos in error.
There are known bugs in delay pools but they > cause very specific low number of multiples or fractions of the > configured pool size - not hundreds of KB faster rates. That's true for the latest version. A few many versions ago there were lots of bugs with https and delay pools. Since he refuses to state the running version I wouldn't discount the possibility. Chico Venancio 2016-08-31 12:23 GMT-03:00 Amos Jeffries <squ...@treenet.co.nz>: > On 31/08/2016 8:13 a.m., erdosain9 wrote: > > Thanks. > > But... > > I'm misunderstanding ? > > Tx , is not the download? > > TX is sent bytes. It depends on what your interfaces mean, but it looks > to me like it is uploads. There are known bugs in delay pools but they > cause very specific low number of multiples or fractions of the > configured pool size - not hundreds of KB faster rates. > > > > > I think it works this way in the mikrotik . That is, the transmission > would > > be the " download " > > So the report you are looking at is measuring the Squid<->client interface? > > Squid delay pools are operating on the Squid<->Server interface traffic. > So they can rate limit your (probably costly) *upstream* bandwidth, not > your internal LAN bandwidth between Squid and clients. > > Amos > > _______________________________________________ > squid-users mailing list > squid-users@lists.squid-cache.org > http://lists.squid-cache.org/listinfo/squid-users >
_______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
