Perlbal as an accelerator for dynamic-but-cachable content

[Chris Hondl]

We've been using memcached directly from our Perlbal instances for caching.
We wrote a plugin to Perlbal that takes inbound URLs, does a tracker lookup
to find a storage node, and then pulls the image from that node.  We used an
async memached client library we had written for an earlier project.  We
cache both lookups against our Mogile trackers and the images pulled from
our Mogile storage nodes.  We run a memcached instance and a Perlbal
instance on each front end machine.    We haven't posted this code any
where, but we could publish if anyone is interested.

Chris

On 10/9/06, Ask Bjørn Hansen <ask at develooper.com> wrote:
>
>
> On Oct 9, 2006, at 18:07, Jake wrote:
>
> > What is LiveJournal (or others) doing to serve up these
> > dynamic-but-cachable requests efficiently? Are they just optimizing
> > dynamic generation (memcached, etc) so it doesn't hurt so bad, and
> > buying additional servers?
>
> Many of us have sites with pages that can be mostly, but not entirely
> cached.   Or sometimes the page can be entirely cached, but you need
> to run a bit of logic to figure out which variant of the page is to
> be served (etc etc).   Doing it in the backend is much easier to
> scale than if you start adding too many smarts to perlbal.
>
>
>   - ask
>
> --
> http://www.askbjoernhansen.com/
>
>
>


-- 
http://avatars.imvu.com/chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.danga.com/pipermail/perlbal/attachments/20061009/a37b1818/attachment.htm