<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks for the link info.<br>
<br>
I literally just set up Varnish for the first time on my web host, so I
am no pro. However, varnish uses a c like scripting language that can
run regexps on the incoming urls and apply rules to them.<br>
<br>
What this means is that we can (as a starting point) choose caching
times for each of those high traffic urls in the varnish script without
touching trac. In the script, we match the front page (with a regexp)
and add a max-cache time to 86400, cache it, etc. <br>
<br>
See <a class="moz-txt-link-freetext" href="http://www.catalystframework.org/calendar/2008/14">http://www.catalystframework.org/calendar/2008/14</a> <br>
for a great varnish tutorial<br>
<br>
By doing that for each of the urls you listed (bar the timeline, which
should be cached for 1 hour or perhaps 30 minutes instead) we will
seriously lighten the load on the database and the webserver, even if
varnish runs on the same machine (as a start).<br>
<br>
Every other url (which doesn't have caching set) we could just cache
for 30 minutes (perhaps even a day), but only for anon users (no
cookies set in browser)<br>
<br>
-Tom<br>
<br>
<blockquote
cite="mid:mailman.97597.1257647916.23374.twisted-python@twistedmatrix.com"
type="cite">
<blockquote type="cite">
<pre wrap="">On 10:41 pm, <a class="moz-txt-link-abbreviated" href="mailto:leyssw@ihug.co.nz">leyssw@ihug.co.nz</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Isn't the simplest option to place a decent reverse proxy between the
webserver and our clients?
</pre>
</blockquote>
<pre wrap="">Possibly so! I gave this a half-hearted attempted a few weeks ago but
quickly gave up. If someone who is familiar with configuring such a
proxy would like to help out, perhaps we can get something useful up
and
running.
</pre>
</blockquote>
<pre wrap=""><!---->
Actually, I just looked at Varnish again and remembered that because of
the way trac sessions work, it's really hard to figure out what may and
may not be correctly cached. I don't know how to resolve this without
serious changes to trac itself.
Jean-Paul
------------------------------
_______________________________________________
Twisted-Python mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a>
<a class="moz-txt-link-freetext" href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a>
End of Twisted-Python Digest, Vol 68, Issue 13
**********************************************
</pre>
</blockquote>
<br>
</body>
</html>