Perrin Harkins wrote:
One thing you didn't mention is why you're using mod_cache at all for
things not generated by mod_perl. Why don't you serve the static
files directly from your front-end server? That's the most common
setup I've seen, with proxying only for mod_perl requests.
Yes, I am only caching mod_perl content. I exclude things like the
static files and images. I cache mod_perl output for performance in
cases like slashdottings (or, these days, links from digg or reddit
etc). The problem is, the site gets so many page requests, that
htcacheclean just seems to be a little overwhelmed.
I'm looking at Squid right now, and have sent a message to their list to
see what they think. At first glance, Squid does seem to have a fairly
big list of configuration directives, so it's possible it might be able
to handle what I need. I'm open to switching, if it turns out that Squid
uses a more scalable cache pruning methodology. I'm a little sad to see
that Apache's mod_cache doesn't seem to even be complete yet - e.g.
directives like CacheGcInterval aren't implemented:
http://httpd.apache.org/docs/2.0/mod/mod_disk_cache.html#cachegcinterval
Maybe Squid is more mature in the caching department... dunno, but worth
a look. I'd appreciate any more experienced people here educating me if
this is wrong.
Thanks again,
Neil
