|
I have set up an LVS managing two servers with rr:
[root@lb1 /root]# ipvsadm -L -n
IP Virtual Server version 0.9.16 (size=16384)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.33.169:80 rr persistent 100
-> 192.168.33.113:80 Route 1 0 0
-> 192.168.33.114:80 Route 1 0 0
ifconfig:
eth0:0 Link encap:Ethernet HWaddr 00:D0:B7:1E:8D:56
inet addr:192.168.33.169 Bcast:192.168.33.169
Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:5 Base address:0xef00 Memory:d0873000-d0873900
(169) is a Virtual IP address.
When I run two test scripts against it (basically a perl for loop with
wget/a bunch of files/) performance is fine,
I get 100Mbits/sec from both machines. System resources on the lvs machine
are fine with just two threads. When I bump this number up to 4 my net
performance drops way down, and load on the lvs goes up to about 50-60%.
(LVS is running all by itself on this server). When I bump it up to 6 or
more, performance is terrible and the LVS get's killed, (like 90-100% system
resources, as reported by top).
I thought we should have no overhead running a DR approach.
ideas?
Jeffrey Schoolcraft
|
