If I understand the code correctly, when I don’t have the cache file,
request is going directly
to upstream, so when I have 100 request at the time when I don’t have
the cache file yet, all
those requests will go to upstream servers, am I correct?
On Tue, Oct 27, 2009 at 01:51:29PM +0100, Tomasz P. wrote:
Hello,
If I understand the code correctly, when I don’t have the cache file,
request is going directly
to upstream, so when I have 100 request at the time when I don’t have
the cache file yet, all
those requests will go to upstream servers, am I correct?
If I understand the code correctly, when I don’t have the cache file,
request is going directly
to upstream, so when I have 100 request at the time when I don’t have
the cache file yet, all
those requests will go to upstream servers, am I correct?
Yes.
Wouldn’t it be better to send only one request, and tell other to wait
for the page when updating is set?
On Tue, Oct 27, 2009 at 02:30:24PM +0100, Tomasz P. wrote:
wait for the page when updating is set?
Yes. This is called “busy locks” in mod_accel, and usually
referenced here under the same name. It’s planned but not
implemented in nginx yet.
I also would love to see this feature implemented, have you had any
progress on this?
Of course I’d be available for testing and feedback.
Thanks, TonyT