倮徽�\毡欢上
Using multiplication:
1500 req/s * 20KBytes * 8 (bits in a Bytes) = 2,4 * 10^8, which is
around 250 Mbits for one way.
This traffic is the traffic from the clients to HAProxy, so you'll
have it twice, since you'll have the same from HAProxy to the servers.
So in total, around 500 Mbits.
cheers
O
how can I calculate if this will work in theory?
On Thu, May 3, 2012 at 5:30 PM, Baptiste wrote:
> Hi,
>
> You'll need one gig interface (two looks better, one for the frontend
> and one for the backend servers), but it should work without any
> issues.
>
> cheers
>
> On Thu, May 3, 2012 at 9:35
Hello Joakim,
What is synced is the persistence (stick) table, not the tcp sessions,
haproxy don't do this, as it is the kernel job to maintains sessions.
However, i know some guys who use keepalived with syncd features to do
that, but never made a test myself...
http://www.austintek.com/LVS
Hi,
I have a
question about replication of sessions.
I have two
haproxy servers (haproxy1 and haproxy2) and try to replicate the sessions with
the
new feature Peers in version 1.5.
It seems to
work fine and I can see the entries in the stick tables on both my servers.
My hope on
t
5 matches
Mail list logo
