memcached as http cache

[googleuser]

Hello,
I have some problems with apache.
If I use squid as proxy-cache I have auth problems. And if I use
mod_cache do not work because mod_cache uses rewrited url and not
requested url (all pages are the same for mod_cache).

These problems are hitting me to implement new http caching engine.
I think that memcached could be useful for this.
Anyone have some experience or info about memcached as http cache
engine. Performance, memory issues, posible implementations,...?

[Perrin Harkins]

If you're talking about static files, it would be slower than your
apache is now. Your OS should be caching files in RAM, which is much
faster than going through memcached to get them.

- Perrin

[Les Mikesell]

I haven't tried it, but this approach sounds fast:
http://www.igvita.com/2008/02/11/nginx-and-memcached-a-400-boost/

But what kind of auth problem do you have with squid?

--
Les Mikesell
lesmi...@gmail.com

[Perrin Harkins]

On Fri, Jul 3, 2009 at 1:58 PM, Les Mikesell<lesmi...@gmail.com> wrote:
> I haven't tried it, but this approach sounds fast:
> http://www.igvita.com/2008/02/11/nginx-and-memcached-a-400-boost/

It sounds faster than dynamically generating pages with Ruby, but not
faster than static pages.

- Perrin

[googleuser]

> But what kind of auth problem do you have with squid?

Apache see squid users as localhost users. Could be posible configure
squid but is difficult.
Another option can be the use of apache module that modify internal
connection settings with fowarded IP, but I can not find a mature
solution.

Dynamic content can be spend 0.4seconds with compression and code
optimize. For this reason is good idea caching.

[Brian Moon]

http://code.google.com/p/memproxy/

It will still be a full proxy. I am not sure what the auth issues are
or why a localhost connection are treated different in this environment
than others. That really sounds like that is your problem and not how
you cache.

Brian.
--------
http://brian.moonspot.net/