Hi Igor,
> ./haproxy -vv
> HA-Proxy version 1.6-dev0-41 2014/07/12
> Copyright 2000-2014 Willy Tarreau <w...@1wt.eu>
>
> Build options :
> TARGET = linux2628
> CPU = native
> CC = gcc
> CFLAGS = -O2 -march=native -g -fno-strict-aliasing
> OPTIONS = USE_LINUX_SPLICE=1 USE_REGPARM=1 USE_OPENSSL=1 USE_STATIC_PCRE=1
>
> Default settings :
> maxconn = 2000, bufsize = 16384, maxrewrite = 8192, maxpollevents = 200
>
> Encrypted password support via crypt(3): yes
> Built without zlib support (USE_ZLIB not set)
> Compression algorithms supported : identity
> Built with OpenSSL version : OpenSSL 1.0.1e 11 Feb 2013
> Running on OpenSSL version : OpenSSL 1.0.1e 11 Feb 2013
> OpenSSL library supports TLS extensions : yes
> OpenSSL library supports SNI : yes
> OpenSSL library supports prefer-server-ciphers : yes
> Built with PCRE version : 8.30 2012-02-04
> PCRE library supports JIT : no (USE_PCRE_JIT not set)
> Built with transparent proxy support using: IP_TRANSPARENT
> IPV6_TRANSPARENT IP_FREEBIND
>
> Available polling systems :
> epoll : pref=300, test result OK
> poll : pref=200, test result OK
> select : pref=150, test result OK
> Total: 3 (3 usable), will use epoll.
>
> 1.5.1 same, after some quests, the load increasing.
Ok, can you "git bisect" this, I'm not sure what else we could do
to pinpoint the issue (as long as you don't have any obvious issues
at build time, like a missing "make clean" before building) ...
Change to the haproxy-1.5 (git) directory and start the bisect like this:
git bisect start
git bisect bad v1.5.1
git bisect good v1.5-dev21
Git will then select a commit approximately "in the middle" between dev21
and v1.5.1 and you can test it. If it works, enter:
git bisect good
otherwise
git bisect bad
and git will select another commit for you to test. In the end (after a few
iterations of the above, git should come up with the bad commit).
Regards,
Lukas
