Hi Lukas, On Tue, Jul 02, 2013 at 09:24:49PM +0200, Lukas Tribus wrote: > Hi! > > > > Hello Willy, > > > > I am still unclear "how could 1 daemon HAProxy process handle > > thousands requests/connections simultaneously or concurrently?" I > > thought the daemon should fork children to handle connections, but I > > could not see any children spawned when did a load-test with 100 > > concurrent users. Could you help me to understand it? > > HAProxy doesn't use multiple processes, threads. Its fully event driven > and does everything with a single process and a single thread. > > You can read more about it in the "Design Choices and history" section > on the website: > http://haproxy.1wt.eu/#desi
Ah you beat me on this one! > Also adding the 10g benchmarks in case you have doubts about the design :) > http://haproxy.1wt.eu/10g.html I hope to have time to update this one with new tests. I've run at 40G a few weeks ago, and I couldn't go beyond by lack of machines :-) I'll retry when I have more time and more hardware. Cheers, Willy
