Hi, On 08.01.2013 19:32, Christian Becker wrote: > Hi Thomas, > > thanks for your quick reply! > >> This looks like your nic cause problems. What nic type is it? > The Server is using Emulex Corporation OneConnect 10Gb NIC (be2net driver).
I saw you have nbproc 34 in the global section. Thats really huge. May I ask what Processor and how many cores it have? >> You could easily add something like >> VERSION="1.5.dev17-patch..." to make, then you know at every time what >> kind of snapshot it was. > Already did that, new versions are now build with a snapshot date ;) > >> A unstable kernel. You use latest and greatest on you own risk. > We´ve picked the kernel since it is officially marked as stable, but i agree, > that it is very new and possibly unstable/buggy. > > Got some other news: > > After removing the option splice-response and option splice-request the cpu > load instantly dropped to a almost normal level. So i guess there are either > in haproxy or in the kernel some splice issues. In the latest snapshots today they were some improvements regarding tcp splicing. > I´m currently building a new kernel with different preemtion settings, i > guess this could also be a cause. > > If this won´t helps either, i´ll try to downgrade the kernel tomorrow to 3.7 > or maybe lower. > > Regards, > Christian > > > > cheers thomas
