is there any difference between a request vs a hit?
772
In metrics such as "requests per second" and "hits per second" for web servers, are the terms "request" and "hit" synonymous? Can you think of a context in which a request is not a hit?
I think the terminology around this is not entirely clear. One interpretation:
One website hit might result in multiple (HTTP) requests, e.g. for the HTML, JS, CSS and images, however it's entirely possibly that the statistic you use will combine all this as one request.
The exact meaning of those terms is context-sensitive. Normally, I'd consider "request" and "hit" to be synonymous.
However, when talking about a caching webserver, a "hit" might refer to a cache hit (as opposed to a "miss"). You might get 10 requests per second, of which 70% are hits (that were able to take advantage of the cache) and the other three requests are misses (that had to be relayed to the upstream server).
I think the terminology around this is not entirely clear. One interpretation:
One website hit might result in multiple (HTTP) requests, e.g. for the HTML, JS, CSS and images, however it's entirely possibly that the statistic you use will combine all this as one request.
When in doubt, read the docs.
The exact meaning of those terms is context-sensitive. Normally, I'd consider "request" and "hit" to be synonymous.
However, when talking about a caching webserver, a "hit" might refer to a cache hit (as opposed to a "miss"). You might get 10 requests per second, of which 70% are hits (that were able to take advantage of the cache) and the other three requests are misses (that had to be relayed to the upstream server).