Hi Dmitry,
On Fri, Sep 11, 2015 at 01:58:42PM +0300, Dmitry Sivachenko wrote:
> For reference: I tracked this down to be FreeBSD-specific problem:
> https://lists.freebsd.org/pipermail/freebsd-net/2015-September/043314.html
>
> Thanks all for your help.
Thanks for the update. What I'm seeing in
> On 8 сент. 2015 г., at 18:33, Willy Tarreau wrote:
>
> Hi Dmitry,
>
> On Tue, Sep 08, 2015 at 05:25:33PM +0300, Dmitry Sivachenko wrote:
>>
>>> On 30 ??. 2015 ??., at 22:29, Willy Tarreau wrote:
>>>
>>> On Fri, Aug 28, 2015 at 11:40:18AM +0200, Lukas Tribus
> On 30 авг. 2015 г., at 22:29, Willy Tarreau wrote:
>
> On Fri, Aug 28, 2015 at 11:40:18AM +0200, Lukas Tribus wrote:
Ok, you may be hitting a bug. Can you provide haproxy -vv output?
>>>
>>>
>>> What do you mean? I get the following warning when trying to use this
Hi Dmitry,
On Tue, Sep 08, 2015 at 05:25:33PM +0300, Dmitry Sivachenko wrote:
>
> > On 30 ??. 2015 ??., at 22:29, Willy Tarreau wrote:
> >
> > On Fri, Aug 28, 2015 at 11:40:18AM +0200, Lukas Tribus wrote:
> Ok, you may be hitting a bug. Can you provide haproxy -vv output?
On Fri, Aug 28, 2015 at 11:40:18AM +0200, Lukas Tribus wrote:
Ok, you may be hitting a bug. Can you provide haproxy -vv output?
What do you mean? I get the following warning when trying to use this
option in tcp backend/frontend:
Yes I know (I didn't realize you are using tcp mode).
Hello,
The flag TCP_NODELAY is unconditionally set on each TCP (ipv4/ipv6)
connections between haproxy and the server, and beetwen the client and
haproxy.
That may be true, however HAProxy uses MSG_MORE to disable and
enable Nagle based on the individual situation.
Use option http-no-delay
Use option http-no-delay [1] to disable Nagle unconditionally.
This option requires HTTP mode, but I must use TCP mode because our
protocol is not HTTP (some custom protocol over TCP)
Ok, you may be hitting a bug. Can you provide haproxy -vv output?
Thanks,
Lukas
On 28 авг. 2015 г., at 12:12, Lukas Tribus luky...@hotmail.com wrote:
Hello,
The flag TCP_NODELAY is unconditionally set on each TCP (ipv4/ipv6)
connections between haproxy and the server, and beetwen the client and
haproxy.
That may be true, however HAProxy uses MSG_MORE to disable
On 28 авг. 2015 г., at 12:18, Lukas Tribus luky...@hotmail.com wrote:
Use option http-no-delay [1] to disable Nagle unconditionally.
This option requires HTTP mode, but I must use TCP mode because our
protocol is not HTTP (some custom protocol over TCP)
Ok, you may be hitting a bug.
Ok, you may be hitting a bug. Can you provide haproxy -vv output?
What do you mean? I get the following warning when trying to use this
option in tcp backend/frontend:
Yes I know (I didn't realize you are using tcp mode). I don't mean the
warning is the bug, I mean the tcp mode is supposed
On Thu, 27 Aug 2015 20:34:35 +0300
Dmitry Sivachenko trtrmi...@gmail.com wrote:
Hello,
we have a client-server application which establish a long-living TCP
connection and generates a lot of small request-response packets which need
to be processed very fast.
Setting TCP_NODELAY on
11 matches
Mail list logo