Question in Load Balancers ( Network Array )

I had a call yesterday with a customer who was asking me if he has a LB that support 100,000 connections how many inbound requests can handle.
I explained that the number of requests could be equal or greater since the established connections are 100,000. But he was asking if there was a way to correlate the “connections” with the “requests”
He has been working with an HTTP proxy ( nginx ) and I guess it accepts”request” not connections.

Also he was asking if the time that the request go from LB to the end back server is about 10ms  ( which is sounds correct ) the round trip is about 50 ms….

If u have any info on any of these two items plz let me know.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

In F5 load balancers, Universal Inspection Engine (UIE) allows you to correlate connections /TCP streams according to the specified data. (Not all data, but rather specific type of load balanced data only)

F5 products do support (specific models) 100,000 concurrent to peak connections. You have to give them a call to get the exact recommendation.

Requests and connections differ in Load balancers as it might be the case that depending on the way LB's are configured single request can serve multiple connections.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Another thing with F5.  If you are using a one connect profile a "connection" is really a request.

One connect allows a single TCP connection to be use for multiple HTTP requests.  This removes the overhead of opening/closing a unique TCP connection for each HTTP request on the F5 to server side.

Unfortunately there is no way that I am aware of to map a request to a connection other than doing a packet capture.
c_hocklandAuthor Commented:
many thanks !!! great info.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.