17 messages in ru.sysoev.nginxRe: Cache questions
FromSent OnAttachments
Jim OhlsteinJul 10, 2009 4:39 pm 
Maxim DouninJul 13, 2009 4:32 am 
Igor SysoevJul 13, 2009 4:48 am 
Jim OhlsteinJul 13, 2009 1:01 pm 
Igor SysoevJul 13, 2009 1:17 pm 
Maxim DouninJul 13, 2009 1:50 pm 
Jim OhlsteinJul 13, 2009 5:44 pm 
Maxim DouninJul 13, 2009 7:29 pm 
Jim OhlsteinJul 13, 2009 8:09 pm 
Igor SysoevJul 13, 2009 10:21 pm 
Jim OhlsteinJul 14, 2009 6:25 am 
Igor SysoevJul 14, 2009 8:10 am 
Jim OhlsteinJul 14, 2009 8:27 am 
Igor SysoevJul 14, 2009 8:41 am 
Jim OhlsteinJul 14, 2009 8:55 am 
Marcus ClyneJul 14, 2009 12:22 pm 
merlin coreyJul 14, 2009 2:37 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Cache questionsActions...
From:Marcus Clyne (macc@gmail.com)
Date:Jul 14, 2009 12:22:50 pm
List:ru.sysoev.nginx

Jim Ohlstein wrote:

Igor Sysoev wrote:

On Mon, Jul 13, 2009 at 11:09:34PM -0400, Jim Ohlstein wrote:

It is now logging "HIT" or "MISS" for each request in that location block.

It is safe to assume that with fastcgi_cache_min_uses set at 2 that for every first miss shared memory is allocated, that the file is written to the cache on the second miss, and that each logged "hit" is an actual serve from the cache (third and subsequent requests for the file)?

Yes. Currently, there are "MISS", "EXPIRED", "STALE", "UPDATING", and "HIT" states. If you will think out a good name for state when miss is just counted, but not cached, I will make this state.

"MISS-NOT_CACHED" fairly well tells the story, if it's not too long. Otherwise "MISS-NC".

Or perhaps "MISS-COUNTING".

Jim

How about "UNCACHED"?

Marcus