What is the acceptable HTTP request-response delay? I have a client-server application that takes 0.4 milliseconds as request-response delay. is this delay acceptable according to the standard?, knowing that there is no distance between the client and the server. please help
Asked
Active
Viewed 1,707 times
1
-
"no distance" means LAN or really close WAN? – hub Mar 26 '13 at 09:55
-
Acceptable to whom or what? – Jenny D Mar 26 '13 at 10:06
-
Huebkov, I mean the client and server in the same machine – mdawaina Mar 28 '13 at 05:33
-
Jenny D, I mean is it acceptable to the end user? – mdawaina Mar 28 '13 at 05:35
1 Answers
0
The admissible delay usually depends on your specific end users requirements, on how the application is going to be used. Only you, or the person that asked you to develop the application, can answer that question.
0.4 milliseconds looks like a very small and very good delay. But it all depends on the context where it is going to be used. If, for example, 100.000 requests needs to be done to actually do something useful with your application, then it will probably not be a very good user experience. Also, take care of how the delay might be changing if simultaneous requests needs to be served at the same time.
There is no such thing a the standard when it comes to HTTP delay. This standard is different for each application and end user context.
Lætitia
- 2,085
- 22
- 33