It can be as simple as doing a curl to your “origin” url (the one you proxy_pass to) for the files you see that gets a lot of MISS’s – if there’s odd headers such as cookies etc, then you’ll most likely experience a bad cache if your nginx is configured to not ignore those headers.
From: nginx <[email protected]> on behalf of Quintin Par <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Saturday, 12 May 2018 at 18.26 To: "[email protected]" <[email protected]> Subject: Debugging Nginx Cache Misses: Hitting high number of MISS despite high proxy valid [https://mailtrack.io/trace/mail/86a613eb1ce46a4e7fa6f9eb96989cddae639800.png?u=74734] My proxy cache path is set to a very high size proxy_cache_path /var/lib/nginx/cache levels=1:2 keys_zone=staticfilecache:180m max_size=700m; and the size used is only sudo du -sh * 14M cache 4.0K proxy Proxy cache valid is set to proxy_cache_valid 200 120d; I track HIT and MISS via add_header X-Cache-Status $upstream_cache_status; Despite these settings I am seeing a lot of MISSes. And this is for pages I intentionally ran a cache warmer an hour ago. How do I debug why these MISSes are happening? How do I find out if the miss was due to eviction, expiration, some rogue header etc? Does Nginx provide commands for this? - Quintin
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
