Sorry I thought it's a completly different thread since it does not
address the check problems at all.
But if it would have been better to leave all those questions in one
thread, I apologize.
The values I'm talking about are the performance examples to be found on
the haproxy website, so not any value Willy posted in this list. Another
thing I should mention is the fact that I'm using pfsense 2.0 in use
with the haproxy package, maybe that could be a problem cause too, I
hope not but just to be sure.
Another thing I'm not sure about is, that the sessions forwarded to my
webservers are one time around 100, so relatively low and at other times
around 700 on every server, and therefor very high, and that within a
few seconds. But neighter the log information nor anything else I've
found could explain this behaviour.
global
maxconn 3000
log 127.0.0.1 local0
uid 80
gid 80
nbproc 2
chroot /var/empty
daemon
listen adserver.adworxs.net
bind 192.168.10.68:80
mode http
log global
option dontlognull
option httpclose
option forwardfor
maxconn 4500
clitimeout 1200000
balance roundrobin
contimeout 1200000
srvtimeout 1200000
retries 10
option httpchk HEAD /www/admin/index.php HTTP/1.0
:q!
# cat haproxy.cfg
global
maxconn 3000
log 127.0.0.1 local0
uid 80
gid 80
nbproc 2
chroot /var/empty
daemon
listen adserver.adworxs.net
bind 192.168.10.68:80
mode http
log global
option dontlognull
option httpclose
option forwardfor
maxconn 4500
clitimeout 1200000
balance roundrobin
contimeout 1200000
srvtimeout 1200000
retries 10
option httpchk HEAD /www/admin/index.php HTTP/1.0
stats enable
stats uri /haproxy?stats
stats realm adserver.adworxs.net
stats auth admin:<pw>
stats show-node
stats refresh s
server adserver1 192.168.10.61:80 check
inter 24000000000000000 weight 101
server adserver2 192.168.10.62:80 check
inter 24000000000000000 weight 101
server adserver4 192.168.10.67:80 check
inter 24000000000000000 weight 100
server adserver5 192.168.10.66:80 check
inter 24000000000000000 weight 100
listen adserver.dev.adworxs.net
bind 192.168.10.70:80
mode http
log global
option dontlognull
option httpclose
option forwardfor
maxconn 1000
clitimeout 120000
balance roundrobin
contimeout 120000
srvtimeout 120000
retries 10
option httpchk HEAD /index.php HTTP/1.0
stats enable
stats uri /haproxy?stats
stats realm adserver.dev.adworxs.net
stats auth admin:<pw>
stats show-node
stats refresh m
server adserver1.dev 192.168.10.41:80 check
inter 240000 weight 100
server adserver2.dev 192.168.10.52:80 check
inter 240000 weight 100
Please ignore the check intervals value, cause I set them rather high
just to get a quick solution for the server check result/down problem.
If the performance is not in direct connection to the server health
check problem, I rather would solve the performance problem first and
afterwards the check problem.
Thank you, I hope this mail gives somewhat more clearity to my problem.
Best regards
Sebastian
On 12.02.2012 12:11, Cyril Bonté wrote:
Hi Sebastian,
Please, help us. You create too many threads at a time for too many
different problems (or sometimes for the exact same issue), where most
of the time the answer is in the documentation.
It's really difficult to follow you. At this time, in this new thread,
I can't guess which configuration your are using, nor I can't guess if
your other issues were solved without having to reread completely
*all* the threads, and I doubt I'm the only one.
Here, you're talking about values Willy posted, this is typically an
email that should stay in that previous thread, then. It would be
easier for everyone.
Thanks for your help, I guess you'll have better answers with such an
effort ;-)
Le 12/02/2012 11:05, Sebastian Fohler a écrit :
I've checked the values Willy posted on the haproxy page. All my
hardware configurations should meet the needs of haproxy. Still I have
major performance problems. How do I best find out why? The logs tell me
not nearly anything I neec to now to fix that problems. Since I use vm's
to try haproxy, I'm able to change some specifics in case I need to.
My Hardware assigned to the vm's is:
Two cores: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz
512 MB Ram
The second problem I have is, as I posted before, down reportings for my
backend server which are definitly not down.
I've run those servers on DNS RR before where each server could handle
at least 700 sessions http connections.
Right now in use with haproxy every server only can keep 300 - 400.
Seems strange to me.
Thank you for any help you can give me.
Best regards
Sebastian
--
Sebastian Fohler
Far-Galaxy Networks
Web: http://www.far-galaxy.de
Tel.: +49 (0)173 8796211
E-Mail: [email protected]
