On Fri, 21 Dec 2007 16:30:52 -0800 (PST)
JustJohnny <johnny.dobbins gmail.com> wrote:
>
> Any community recommendations on types of upstream
caching for django/
> dynamic sites? (besides the standard "the docs
say....")
>
> Any pros/cons on a squid (http://www.squid-cache.or
g/) vs varnish
> (http://varnish.pro
jects.linpro.no/) setup? Looking for solution to
> front 3-5 django application servers with psql backend
and hit rates
> of 500,000 to 1,000,000 / hour.
>
> Thanks for any ideas or remarks on your experience!
We are/will be using one squid per webserver that caches
static content (including javascript, css and user supplied
files).
Expiration Date is set to several years and whenever
something changes
we just increase the version number of the file [1]. Users
cannot change
their files they have to reupload it so it gets a new id and
a new
filename. Theoretically you wouldn't even need a squid for
static
content like that cause the content should be cached in the
browsers
cache but you don't want users that use a very small cache
to hit the
application servers all the time.
The actual pages are cached within django cause at least a
small
fraction of each page is always generated dynamically.
Works like a charm, althought I haven't looked at varnish
yet, perhaps I
should.
[1] http://developer.yahoo.com/performance/rules.html#expir
es
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-users googlegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribe googlegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
|