We are trying to measure times using the variables referred on the following article and on the emails above: https://www.nginx.com/blog/using-nginx-logging-for-application-performance-monitoring/#var_request_time But It came to our attention that those are not accurate, our log file: log_format main ‘“$request_time" - $upstream_response_time” - “$upstream_connect_time” - “$uby joao.pereira - Nginx Mailing List - English
Hi Peter and Reinis, I do have have a lot of cache, currently I have ~45 millions of keys and its the beginning of our tests which I believe will get close to the 80 million you say. I will add some tests I have done, I set up flash (a python framework) that delays a response for 5 second then I do the request using my nginx as a proxy. The max-age is set to 1 second to force nginx to go tby joao.pereira - Nginx Mailing List - English
Just to add more information, I also have: proxy_cache_use_stale error timeout invalid_header updating http_500 http_502 http_503 http_504by joao.pereira - Nginx Mailing List - English
Hi all, I'm trying to set up an nginx with a big amount of disk to serve as a cache server. I have the following configuration: proxy_cache_path /mnt/cache levels=2:2:2 keys_zone=my-cache:10000m max_size=700000m inactive=30d; proxy_temp_path /mnt/cache/tmp; On my logs I can see that HIT's are very fast but STALEs take as much as MISS while I believe they should take as much as HITs.by joao.pereira - Nginx Mailing List - English