Re: Hitting rate limit?

Are you using keepalives? If not, you're measuring mostly the TCP/SSL set up and teardown times. Try ab -k. I did some measurements recently on a web system and got 7 kreq/s for a non-SSL site without keepalives and 30kreq/s with. -- Hubert Matthews

Re: Hitting rate limit?

Hi Atha, Atha Kouroussis wrote: > Output from ab against haproxy: > Concurrency Level: 200 > Time per request: 49.986 [ms] (mean) If you check these numbers, you'll notice that with a time of 49 ms per request and 200 concurrent requests, you;ll end up at exactly 4000 requests /

Re: Hitting rate limit?

Hi Aleks, On Tue, Jan 17, 2017 at 8:55 AM, Aleksandar Lazic wrote: > Hi. > > Am 17-01-2017 05:46, schrieb Atha Kouroussis: > > Hi all, >> >> I seem to hitting some kind of bottleneck at about 4k req/s and I'm not >> able to find the cause. >> >> I have HAproxy 1.7.2

Re: Hitting rate limit?

Hi. Am 17-01-2017 05:46, schrieb Atha Kouroussis: Hi all, I seem to hitting some kind of bottleneck at about 4k req/s and I'm not able to find the cause. I have HAproxy 1.7.2 installed on Ubuntu 16.04.1, VM with 8 cores, 2GB RAM, 1 Gbps networking. Testing with ab cannot get past ~4K

Hitting rate limit?

Hi all, I seem to hitting some kind of bottleneck at about 4k req/s and I’m not able to find the cause. I have HAproxy 1.7.2 installed on Ubuntu 16.04.1, VM with 8 cores, 2GB RAM, 1 Gbps networking. Testing with ab cannot get past ~4K req/s. Hitting the backend directly can yield 8-10K without