Thanks, a configuration such as below works great for the iperf load
defaulting to port 5001.
Apologies for the newbie question. Details are certainly described in the
documentation, I just had a hard time seeing past all the HTTP related items.
-Steen
defaults
timeout connect 5000ms
timeout client 50000ms
timeout server 50000ms
listen ipgw 192.168.3.101:5001
mode tcp
balance roundrobin
server server1 192.168.128.201:5001
server server2 192.168.128.202:5001
-----Original Message-----
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: Saturday, April 30, 2011 3:43 AM
To: Larsen, Steen
Cc: haproxy@formilux.org
Subject: Re: non-http load balancing configuration.
Hi Steen,
On Fri, Apr 29, 2011 at 11:30:15AM -0700, Larsen, Steen wrote:
> Hi, I would like to do some performance testing without http in a
> configuration of 5 machines such as below using iperf:
>
>
>
> ClientA --- LB1 ---ServerA
>
> ClientB -- - ServerB
>
>
>
> The load balancer routes between two subnets, clients on one subnet and
> servers on the other subnet.
>
>
>
> I would like to have two iperf server processes each listening on the same
> TCP socket number (i.e 5000).
>
>
>
> When clientA starts a client session to the LB1 IP address, HAProxy relays to
> serverA. Later, when client starts an iperf client session to LB1, the proxy
> should use ServerB as a relay target. As clients and servers scale up in
> count, I presume a basic round-robin would work.
>
>
>
> In the documentation and mailing list there is a lot of detail on http and
> security related proxy details, but I am not finding a clear description on
> setting up such a configuration. Any suggestions on config options are
> greatly appreciated.
In fact, what you want is the most basic setup. You'd just have this :
listen mylb
mode tcp
bind <ip:port>
balance roundrobin
server a <ip:port>
server b <ip:port>
You probably don't need the checks nor whatever in a test configuration.
However, I strongly encourage you to set up a second listener in HTTP mode to
report the stats. It's very convenient during tests, as it gives you a summary
of connection errors and such.
Regards,
Willy
