So as you guys said: it's a normal behavior of nginx and the problem is how
can I monitor response time exactly?because, when I request a static link (a
jpeg i.e), it take about 3s to completely download, but request_time still
0.000, and because it's a HIT request so I dont have upstream_response
> - a cache hit means that the resource should also be in the linux
page cache - so no physical disk read needed.
That's a very wrong assumption to make, and only makes sense in very
small scale setups - and multiple terabytes of memory isn't exactly
cheap, that's why we have SSD storage to ha
This might not be a bug at all. Remember that when nginx logs request
time it's doing so with millisecond precision. This is very, very
coarse-grained when you consider what
modern hardware is capable of. The Tech Empower benchmarks shwo that an
(openresty) nginx on
a quad-socket host can server
Hello!
On Thu, Jun 22, 2017 at 05:53:04AM -0400, jindov wrote:
> I've configured for nginx to cache static like jpeg|png. The problem is if
> request with MISS status, it will show a non-zero value request_time, but if
> a HIT request, the request_time value is 0.000.
This is expected behaviour.
Hi guys,
I've configured for nginx to cache static like jpeg|png. The problem is if
request with MISS status, it will show a non-zero value request_time, but if
a HIT request, the request_time value is 0.000.
This is an nginx bug and is there anyway to resolve it.
My log format
```
log_format c
