> On Sep 12, 2019, at 4:57 PM, Bryan Call wrote:
>
> I would double check your buffer settings just in case:
> $ sysctl -a | grep tcp | grep mem
> net.ipv4.tcp_rmem = 4096 87380 6291456
> net.ipv4.tcp_wmem = 4096 16384 4194304
>
> $ traffic_ctl config match buffer
> proxy.config
I would double check your buffer settings just in case:
$ sysctl -a | grep tcp | grep mem
net.ipv4.tcp_rmem = 409687380 6291456
net.ipv4.tcp_wmem = 409616384 4194304
$ traffic_ctl config match buffer
proxy.config.net.sock_send_buffer_size_in: 2097152
proxy.config.net.sock_recv_
> On Sep 12, 2019, at 10:28 AM, Bryan Call wrote:
>
> I am interested in ESNI and I think it would be a great feature to have in
> ATS. I would be willing to test changes in a production environment.
Yeh, I think this would be of wide interest for the general ATS community.
— Leif
>
>
Bryan,
Thanks for the response. Good reminder about the tranmission buffer limiting
the TCP tranmission window
which needs to be sized for the bandwidth delay product. I am a L2/L3 guy so
not a TCP expert :-).
However, I don't know whether the default (I believe 1MB in our RHEL release)
causes
I am interested in ESNI and I think it would be a great feature to have in ATS.
I would be willing to test changes in a production environment.
-Bryan
> On Sep 11, 2019, at 7:33 AM, Hans-Christoph Steiner
> wrote:
>
>
> Hey all,
>
> I'm working with Stephen Farrell who is part of the IETF
I have seen issues where you can’t reach the max throughput of the network
connection without increasing the TCP buffers, because it effects the max TCP
window size (bandwidth-delay product). Here is a calculator I have used before
to figure out what your buffer size should be:
https://www.swi
