What is considered fast performance for a single server request? -


I understand that there are many factors involved in making DB calls and the Internet, but I strongly recommend the methods Referring to the customer, roundtrip I am using a stopwatch to get an average range but I do not know what is generally considered to be fast or decent performance. 10ms 500ms?

This is actually a subjective question, but I think it's valid. We all know that the speed of 4 miles per hour for the car is slow, while 150 miles per hour - lets go back to the server very fast now. DB takes about 20 ms faster (indexed) call Suppose we have them 5 is required. Storage latency is also about 5-10 milliseconds in which data data megabytes are throughput per second. Let's say that we need to read 1 MB should say that 10 milliseconds of 50 millisecond cpu is enough to create dozens of searches in different maps. Some of the 10-20 results are sufficient to fill the template effectively. That's why we get 20 * 5 (for DB) + 50 (file system) + 10 (in memory searches) +20 (template-filling) amount. So 180 milliseconds, we can assume that the efficient server is not overloaded, it should be about 200 milliseconds if the data is not highly scanned. From the top we can also assume that at least 50 get - very challenging. Of course the above versions depend on many factors, but the goal of the post - to feel something that is fast and which is slow.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -