Hi,
maybe you need to increase ulimit and max connections in haproxy config.
Am 12.05.18, 15:54 schrieb "Jarno Huuskonen" :
Hi,
On Fri, May 11, Marco Colli wrote:
> >
> > Do you get better results if you'll use http instead of https ?
>
>
Hi,
On Fri, May 11, Marco Colli wrote:
> >
> > Do you get better results if you'll use http instead of https ?
>
>
> I already tested it yesterday and the results are pretty much the same
> (only a very small improvement, which is expected, but not a substantial
> change).
Couple of things to
>
> Do you get better results if you'll use http instead of https ?
I already tested it yesterday and the results are pretty much the same
(only a very small improvement, which is expected, but not a substantial
change).
Running top / htop should show if userspace uses all cpu.
During the
>
> Maybe you want to disable it
Thanks for the reply! I have already tried that and doesn't help.
Maybe you can run a "top" showing each CPU usage, so we can see how much
> time is spent in SI and in userland
During the test the CPU usage is pretty constant and the values are these:
%Cpu0
Hi,
On Fri, May 11, Marco Colli wrote:
> Hope that this is the right place to ask.
>
> We have a website that uses HAProxy as a load balancer and nginx in the
> backend. The website is hosted on DigitalOcean (AMS2).
>
> The problem is that - no matter the configuration or the server size - we
>
>
> Solution is to have more than one ip on the backend and a round robin when
> sending to the backends.
What do you mean exactly? I already use round robin (as you can see in the
config file linked previously) and in the backend I have 10 different
servers with 10 different IPs
sysctl
Hi Marco,
I see you enabled compression in your HAProxy configuration. Maybe you want
to disable it and re-run a test just to see (though I don't expect any
improvement since you seem to have some free CPU cycles on the machine).
Maybe you can run a "top" showing each CPU usage, so we can see how
Check how many connections you have opened on the private side(i.e.
between haproxy and nginx), i'm thinking that there are not closing fast
enough and you are reaching the limit.
Best regards,
Mihai
On 5/11/2018 4:26 PM, Marco Colli wrote:
Another note: each nginx server in the backend can
Another note: each nginx server in the backend can handle 8,000 new
clients/s: http://bit.ly/2Kh86j9 (tested with keep alive disabled and with
the same http request)
On Fri, May 11, 2018 at 2:02 PM, Marco Colli wrote:
> Hello!
>
> Hope that this is the right place to
Hello!
Hope that this is the right place to ask.
We have a website that uses HAProxy as a load balancer and nginx in the
backend. The website is hosted on DigitalOcean (AMS2).
The problem is that - no matter the configuration or the server size - we
cannot achieve a connection rate higher than
10 matches
Mail list logo