On 4/5/07, Zed A. Shaw <[EMAIL PROTECTED]> wrote:
>
> On Thu, 05 Apr 2007 08:20:14 -0700
> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> >
> > There are some potential disadvantages of a system like this. It
> > fundamentally violates shared nothing, which means you cannot scale to
> > infinity with this, but it can likely scale to somewhere around 95th
> > percentile of all internet websites...
>
> That's another point I forgot to make:  this should be a last resort.
> I hate the word "should" but really, if you haven't tried to tune up a
> basic shared-nothing design to the fastest you can before running
> toward insanely complex caching designs then you've gone in the wrong
> direction.

I agree, complex is bad and should be the last thing you worry about.
But it seems like if you want to do decent page caching in a clustered
rails setup, you have two options, both of which are complex in their
own way:

* just page cache on each web server, and then handle expiration by
kicking off jobs across the network on the other machines to remove
stale content.  So each server has its own copy of the cache, and we
keep things in sync through some annoying but simple scripts.  Or if
we dont care too much about stale content, remove the page cache on a
time based schedule across the servers...if its short enough our
visitors won't notice or won't care.

* share a single page cache across the cluster via NFS/GFS/etc, which
adds all complexity and issues you guys have discussed.

Or just say screw it, and use action/fragment caching in memcached.

> Many, many times I've seen simple little changes and tweaks with bits
> of strategic rework and caching boost a site that had a good initial
> shared-nothing design way beyond what a heavy shared cache site could
> pull off.

Definitely - I'm amazed how many sites aren't using any http
compression yet, even w/ mod_deflate being core apache for years now.
I also wonder how many sites are still using the default apache conf
file, with all those unneeded modules loaded...

- Rob

-- 
http://robsanheim.com
http://seekingalpha.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to