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 Also adding the 10g benchmarks in case you have doubts about the design :) http://haproxy.1wt.eu/10g.html Lukas
