test: 3 backend servers each max 8k
PV/s for 12,5 kB file we got max 6k PV/s.
--
Regards
Dominik
___
Od: Willy Tarreau [w...@1wt.eu]
Wysłano: 1 kwietnia 2012 20:27
Do: Mostowiec Dominik
DW: haproxy@formilux.org
Temat: Re: ODP: tcp resets on reload haproxy
Hi D
On Wed, Apr 04, 2012 at 09:08:25AM +0200, Mostowiec Dominik wrote:
> Hi,
> > Krisztian Ivancso is working on FD passing
> How long will it take?
No idea, it's experimental right now so it may take some time before
it's finished and mergeable. We might also encounter complex issues
inherent to the
Hi,
> Krisztian Ivancso is working on FD passing
How long will it take?
--
Regards
Dominik
-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: Wednesday, March 21, 2012 7:46 AM
To: Mostowiec Dominik
Cc: haproxy@formilux.org
Subject: Re: tcp resets on reload haproxy
Hi Dominik,
On Sun, Apr 01, 2012 at 01:43:31PM +0200, Mostowiec Dominik wrote:
> Hi,
>
> >> maxconn 163937
> > What's the reason for this magic number ?
> It's random :-)
OK
> > Did you notice that your request packet (the 4th) was lost on the network ?
> > I guess you captured on the siege
what you intend to do, but it will generally
> not bring anything and might even reduce the performance.
I have 2x6 core server (24 core in ht).
-
Regards
Dominik
________________
Od: Willy Tarreau [w...@1wt.eu]
Wysłano: 31 marca 2012 18:58
Do: Mostowiec Dominik
DW: haproxy@formil
Hi Dominik,
On Fri, Mar 30, 2012 at 03:52:20PM +0200, Mostowiec Dominik wrote:
> Hi,
> Thanks for the response.
>
> I have another problem:
>
> 11:20:58.713922 IP siege_host.46589 > loadbalancer.8123: Flags [S], seq
> 1849604553, win 14600, options [mss 1460,nop,wscale 4], length 0
> 11:20:58.71
On Thu, Mar 22, 2012 at 01:01:50AM +0100, Mariusz Gronczewski wrote:
> 2012/3/21 Willy Tarreau :
> >> Can I do something to fix this?
> >
> > Krisztian Ivancso is working on FD passing between the old and the new
> > process, which should catch most of these issues. The difficulty remains
> > in id
2012/3/21 Willy Tarreau :
>> Can I do something to fix this?
>
> Krisztian Ivancso is working on FD passing between the old and the new
> process, which should catch most of these issues. The difficulty remains
> in identifying which FD can be reused and possibly adjusted when a number
> of options
Hi,
On Tue, Mar 20, 2012 at 03:30:18PM +0100, Mostowiec Dominik wrote:
> Hi,
> When I stress testing haproxy and reload it with -sf option:
> "The server is now under siege...[error] socket: unable to connect sock.c:222:
> Connection reset by peer
> [error] socket: unable to connect sock.c:222: Co
Hi,
When I stress testing haproxy and reload it with -sf option:
"The server is now under siege...[error] socket: unable to connect sock.c:222:
Connection reset by peer
[error] socket: unable to connect sock.c:222: Connection >
[error] socket: unable to connect sock.c:222: Connection >
...
"
It s
10 matches
Mail list logo