At HAproxy.com, we use the following: - httpterm as a web server: http://1wt.eu/tools/httpterm/ - inject as a client: http://1wt.eu/tools/inject/
Baptiste On Fri, Feb 6, 2015 at 2:59 AM, Dennis Jacobfeuerborn <denni...@conversis.de> wrote: > On 05.02.2015 20:09, Baptiste wrote: >> On Thu, Feb 5, 2015 at 4:54 PM, Klavs Klavsen <k...@vsen.dk> wrote: >>> Baptiste wrote on 02/05/2015 04:44 PM: >>> [CUT] >>>> >>>> >>>> 3000 req/s in clear is low and a so rounded number is not normal :) >>>> Move (far far) away from this provider. >>>> >>>> You're wasting your time investigating perfomance issue while the >>>> limitation is in the hypervisor and multitenancy of your supplier. >>>> >>> it's running on vmware 5.5 on local hardware - nowhere else to go :( >>> >>> If I set haproxy to just send a 301 response (ie. not relay to varnish >>> delivering the favicon.ico) - I get approx 15k req/s.. >>> >>> >> >> this is very low.... We can get more than 50K conn/s in our VMWare lab >> using our HAProxy based ALOHA appliance. >> you must have an issue somwhere. > > Are there any best practices on how to test haproxy in this regard? What > are the recommended tools and settings to make a realistic conn/s test? > > Regards, > Dennis > >
