I am trying to access images by Everything HTTP service.
My application will try to calibrate URL link with http response.
URL sample :
http://30.222.123.99/E%3A/OBRIMAGE/OUT/ ... 0000-2.jpg
calibration target part :
202108051229 -> YYYYMMDDHH24MI
if above URL http response = 404,
my application will try again with
http://30.222.123.99/E%3A/OBRIMAGE/OUT/ ... 0000-2.jpg
or
http://30.222.123.99/E%3A/OBRIMAGE/OUT/ ... 0000-2.jpg
if http response = 200 (image found), this image URL calibration will end.
i have maximum 450 URL per minute (worst case) need to do calibration, mean maximum 450*3 = 1250 http request will send to Everything.
Can it handle ? What is the maximum http request per second Everything can handler ?
thank you for your assist.
What is the maximum http request per second Everything can handler ?
Re: What is the maximum http request per second Everything can handler ?
I can't answer your question, but I would suggest to just try it. Everything is very fast, but nobody here knows how fast your hardware and infrastructure are.
Some other suggestions, as I suspect talking to a webserver this way is sub-optimal (but that is without knowing the exact workflow)
- Combine the searches: ( | means OR)
- Use the SDK instead to integrate your queries in your program or even the command-line interface ES. That might eliminate some overhead and therefor improve speed.
When using the aformentioned search, you will get a reply with which one matches that query
Some other suggestions, as I suspect talking to a webserver this way is sub-optimal (but that is without knowing the exact workflow)
- Combine the searches:
202108051228 } 202108051229 | 202108051230- Use the SDK instead to integrate your queries in your program or even the command-line interface ES. That might eliminate some overhead and therefor improve speed.
When using the aformentioned search, you will get a reply with which one matches that query
Re: What is the maximum http request per second Everything can handler ?
The HTTP server should be able to handle 10,000 requests per second.
Above that, you will likely run into winsock2 limitations.
There is a db query behind each request, so the limit is more realistically around 100-1000 requests per second.
My suggestion is to just send as many requests to the HTTP server and see what happens.
You will most likely get connection failures as the winsock connection buffer is full.
-If there is a connection failure, simply re-add the request to a queue and try again.
Or, you will get read timeouts as Everything is busy performing other queries.
Note: Everything will only perform one db request at a time.
Other requests will block until the database becomes available.
Above that, you will likely run into winsock2 limitations.
There is a db query behind each request, so the limit is more realistically around 100-1000 requests per second.
My suggestion is to just send as many requests to the HTTP server and see what happens.
You will most likely get connection failures as the winsock connection buffer is full.
-If there is a connection failure, simply re-add the request to a queue and try again.
Or, you will get read timeouts as Everything is busy performing other queries.
Note: Everything will only perform one db request at a time.
Other requests will block until the database becomes available.