You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to mod_cache
I'm running a site that was recently slammed - 180,000 unique visitors
yesterday.
Lighty + mod_cache saved my pants! So thank you to everyone involved.
My setup is to have lighty in "front" of an apache based php site
I've noticed some behavior that stresses the system when a cached file
is expired. It seems that when a cached file is expired, if
additional requests come in for that file between the time the first
request hit the backend and the time the cache is repopulated, they
all go through to the backend. This causes "rushes" against the
backend - behaving as if the caching server isn't there at all. There
also appears to be some conflict opportunity on cache writing? It
seems like these "rushes" that I'm getting dont' resolve quickly and
can go on for a minute or so.
I'm also seeing "fatal error"s on these files presumably due to the
file being deleted before the sendfile actually gets around to finding
it.
Below are snippets from my lighty config and error.log (with cache
debug enabled).
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to mod_...@googlegroups.com
Modcache keeps list of urls which are handled to avoid serveral connections writing to one cache file at the same time. That's the reason of "somebody is handling /root/taxes/lighty/cache/www.electiontaxes.com/jscomments.php now^M" in lighttpd error logfile