trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Balsa <>
Subject Re: plugging into the backside of ATS?
Date Fri, 27 May 2011 22:29:43 GMT
I started messing around with a protocol plugin
of the memcached protocol on top of the TS cache (sounds like John
beat me to it). Think that could be way cooler (persistant, protocol
compatible, high performing, large object support, etc) than TS
caching to memcache.

Don't forget the 1MB limit on memcached "objects". I'm pretty sure you
can increase that, but I think it's compile time IIRC:


On Fri, May 27, 2011 at 2:37 PM, John Plevyak <> wrote:
> Just an FYI, the clustering support in the proxy right now is optimized for
> some non-obvious case: very
> large documents are streamed in chunks, and header matching occurs on the
> cache which contains the
> document which minimizes round trips, staging to disk handles the long tail,
> etc.
> I think that you will find that replacing the disk cache with memcache will
> not improve performance and
> will likely run into some subtle problems.  However, I am interested to see
> the results.   BTW: I have
> a memcache on TS implementation around somewhere, for a persistent
> memcached.
> john
> On Fri, May 27, 2011 at 12:28 PM, Earle, Erik <> wrote:
>> Is there a good starting point for looking at plugging into the internals
>> of ATS.
>> For example, suppose I wanted to replace the default caching mechanism
>> with memcache or add a full http client (like libcurl) without blocking in a
>> continuation callback thread.

View raw message