The implication being that if you need a distributed cache, you should try our clustering features.
Cheers, -- leif On May 27, 2011, at 3:37 PM, John Plevyak <[email protected]> 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 <[email protected]> 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. > > > > > > > >
