Hi Baptiste. Yeah, I am not focusing much on the timeout values.
Current top performance that we have got from a m1.xlarge on amazon ec2 is: 2000 conns/s ~30k active connections (with good response time) 8000 req/s Using "taskset" to set haproxy on cpu 01 and then have stud on 00,02,03. That turned out to be the best setup during our loadtests. Using haproxy on cpu 00 resulted in a lot of load on the virtual layer (si%). Much better to have haproxy on cpu 01 and let stud use cpu 00 instead. /E -----Original Message----- From: Baptiste [mailto:[email protected]] Sent: den 1 november 2011 13:17 To: Erik Torlen Cc: [email protected] Subject: Re: Timeout values Hey Erik :) Once again, playing with the timeout below won't change anything. Try playing with server maxconn, some sysctls also has to be checked. What kind of performance can you get? Are you sure your bottleneck is your LB? cheers On Tue, Nov 1, 2011 at 7:33 PM, Erik Torlen <[email protected]> wrote: > I'm trying to see what difference the values does to my loadtest result. The > web platform is on amazon > so the latency and everything is having a "certain" impact on the result. > > I will keep testing and see what kind of result I get. Currently I have > another problem which I will > send in to the list :/ > > /E > > -----Original Message----- > From: Baptiste [mailto:[email protected]] > Sent: den 25 oktober 2011 23:15 > To: Erik Torlen > Cc: [email protected] > Subject: Re: Timeout values > > Hi Erik, > > What's your purpose here? > Depending on your load test and you haproxy configuration, the queue > timeout might generate 503 responses. > The other ones are related to the behavior you want for your web platform. > Basically, all the values you added seems too high. > > > Cheers > > > On Tue, Oct 25, 2011 at 11:02 PM, Erik Torlen > <[email protected]> wrote: >> Hi, >> >> I would like to get feedback on these timeout values. >> >> timeout http-request 40s >> timeout queue 1m >> timeout connect 120s >> timeout client 1m >> timeout server 1m >> timeout http-keep-alive 40s >> timeout check 40s >> >> I have done alot of different loadtests with different values using stud in >> front of haproxy and backend on separate instances >> in the cloud (meaning there is higher latency then normal against backend). >> >> Can't see any big difference in the loadtest result when having these >> timeout fairly high. I guess that really low values will affect >> the loadtest result more. >> >> /E >> >> >
