i dont know how high performance your system is but i think you can try
the new version 3.1.10 on your system and after you will get real
performance
issues you can try to recompile it with less strick option.. or .. just
compile one with limit and one without limit and change the binary if
you dont get results.
as long as i know 64k is really more then many systems needs for a buffer.
On 31/01/2011 11:57, Jack Falworth wrote:
Hi squid-users,
I have a question regarding the TCP send/receive buffer size Squid uses.
For my high-performance setup I increased both buffer sizes on my Ubuntu 10.04 system. Unfortunately I found out that Squid 2.7 (as well as 3.x) limits the receive buffer to 64K and the send buffer to 32K in the configure.in script.
In addition I found this bug report regarding this check:
http://bugs.squid-cache.org/show_bug.cgi?id=1075
I couldn't really figure out the problem with Squid using higher buffer sizes if it is the intention of the administrator to increase those values.
This check was included in CVS rev. 1.303 back in 2005, thus it's quite old.
Is this some legacy check or is it still important with today's systems?
Can I safely remove this check or will this have some side-effects, e.g. say the some internal data structures won't be able to cope with higher values?
Regards,
JackF
