[squid-users] Squid performance not able to drive a 1Gbps internet link
Heiler Bemerguy
heiler.bemerguy at cinbesa.com.br
Wed Aug 3 14:32:40 UTC 2016
I think it doesn't really matter how much squid sets its default buffer.
The linux kernel will upscale to the maximum set by the third option.
(and the TCP Window Size will follow that)
net.ipv4.tcp_wmem = 1024 32768 8388608
net.ipv4.tcp_rmem = 1024 32768 8388608
--
Best Regards,
Heiler Bemerguy
Network Manager - CINBESA
55 91 98151-4894/3184-1751
Em 03/08/2016 06:45, Marcus Kool escreveu:
>
>
> On 08/03/2016 12:30 AM, Amos Jeffries wrote:
>
>
>> If thats not fast enough, you may also wish to patch in a larger value
>> for HTTP_REQBUF_SZ in src/defines.h to 64KB with a matching incease to
>> read_ahead_gap in squid.conf. That has had some mixed results though,
>> faster traffic, but also some assertions being hit.
>
> I remember the thread about increasing the request buffer to 64K and it
> looked so promising.
> Is there any evidence of setting HTTP_REQBUF_SZ to 16K is stable in
> 3.5.x?
>
> Marcus
>
>> You may find that memory becomes your bottleneck at higher speeds.
>> 8-16GB sounds like a lot for most uses, but when you have enough
>> connections active to drive Gbps (with 4-6x 64KB I/O buffers) there are
>> is lot of parallel pressures on the RAM.
>>
>> Amos
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
More information about the squid-users
mailing list