I have an application internal to my company that needs to be very fast per client, because the clients are so limited and the whole thing is internal.
So, the client is expected to send so many concurrent requests and what I want nginx
to do is putting as much parallelism into that as possible. Yes, that's exactly the opposite of what people normally do. Wherever I searched, people are asking of limiting connections per IP, thus mitigating attacks, etc. I want the exact opposite.
I can't really understand what's happening in nginx
regarding that. What I tried to do is testing its behavior by having a simple server that just sleeps for 10 seconds and returns a string, and I curl
ed it from 5 different terminals. The numbers where 10 seconds, 18 seconds, 21 seconds, 25 seconds, 30 seconds. So there is some sort of queuing happening, but not really sequential (otherwise it was supposed to be 10 seconds, 20 seconds, 30 seconds, 40 seconds, 50 seconds). But, it's not fully parallel either!
I hope this clarifies what I want... please advise.