RE: [Zope] Caching/http-acceleration and proxying Zope-served content
not sure if thats what you want, but squid _can_ act as a frontend to multiple backend-servers. check out the squid users guide (http://squid-docs.sourceforge.net/latest/html/book1.htm) specifically http://squid-docs.sourceforge.net/latest/html/x2544.htm which deals with "accelerator" options peter. On Mon, 8 Jan 2001 [EMAIL PROTECTED] wrote: :Hmm. That's been my thought on squid as well, given its ground-up design :for caching in the first place. My worry, though, is that with squid I lose :support for virtual hosts on seperate boxes, because I need to support Zope, :static content, and some legacy stuff running ColdFusion on an NT box. My :impression is that Squid's http accelerator mode (inverse transparent proxy, :or whatever you want to call it) is somewhat of an afterthought compared to :the standard proxy use case. If it supports the ability to direct traffic :based upon the virtual host address, then squid works - if not, I think I :have to go the Apache route... I also wonder just how good Apache's :mod_proxy caching is? Any thoughts? : :Sean : :-Original Message- :From: Shane Hathaway [mailto:[EMAIL PROTECTED]] :Sent: Monday, January 08, 2001 12:59 PM :To: [EMAIL PROTECTED] :Subject: Re: [Zope] Caching/http-acceleration and proxying Zope-served :content : : :[EMAIL PROTECTED] wrote: : : I have a question, for anyone experienced in working with Zope and caching : proxies: : : I'm setting up a load-balanced server farm that has nodes that will run : Apache and proxy (via mod_proxy) to ZEO clients running ZServer. This :farm : is routed (both ways) through a layer 4 load-balancing appliance, and all : these boxes (both nodes and the balancer) are sitting inside a DMZ with : private IP addresses. The public world will access these servers via a : firewall box running transparent proxy (actually, I guess, similar to : squid's http_accel mode; the semantics here are a bit tricky, as it's more : of a inverse trans-proxy). Between Apache and Zope, there would be :several : virtual hosts, and I'd be using the SiteAccess product. It gets a bit : tricky in that I need to access several different virtual hosts inside the : DMZ (one for the ZEO farm, and another for a dedicated CGI-based ad server : on another box) via the proxy. A more detailed (ascii art) diagram of :what : I am trying to do, is at http://209.132.8.98/server_ascii_art.txt : : My question is this: does anybody have any thoughts on the merits of Squid : (http accelerator mode) versus Apache/mod_proxy in terms of caching, :virtual : hosts, and the like when working with Zope sites? Any big pitfalls to :this : kind of setup with Zope sites? : :I would prefer Squid since its only purpose in life is caching. It :follows the "do one thing and do it well" mantra. : :But whatever your choice, I hope you make use of the new CacheManagement :feature in Zope 2.3. It is designed to make things like this :straightforward and easy. There's a recent news announcement that links :to everything you need--including complete help docs! : :Shane : :___ :Zope maillist - [EMAIL PROTECTED] :http://lists.zope.org/mailman/listinfo/zope :** No cross posts or HTML encoding! ** :(Related lists - : http://lists.zope.org/mailman/listinfo/zope-announce : http://lists.zope.org/mailman/listinfo/zope-dev ) : :___ :Zope maillist - [EMAIL PROTECTED] :http://lists.zope.org/mailman/listinfo/zope :** No cross posts or HTML encoding! ** :(Related lists - : http://lists.zope.org/mailman/listinfo/zope-announce : http://lists.zope.org/mailman/listinfo/zope-dev ) : -- _ peter sabaini, mailto: [EMAIL PROTECTED] - ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] Caching/http-acceleration and proxying Zope-served content
I started using mod_proxy, because I needed the configuration options (redirection etc.) and squid wouldn't cache ssl stuff. It's running very well since about six months now. The downside is that it's really badly documented. BTW there is a new book by Ralf Engelschall that you can download for free from http://www.apacheref.com that also covers mod_proxy. Not in detail though. He calls mod_proxy apache's stepchild. Concerning numbers I gave some in my caching with mod_proxy howto (http://www.zope.org/Members/rbeer/caching). Ragnar Hmm. That's been my thought on squid as well, given its ground-up design for caching in the first place. My worry, though, is that with squid I lose support for virtual hosts on seperate boxes, because I need to support Zope, static content, and some legacy stuff running ColdFusion on an NT box. My impression is that Squid's http accelerator mode (inverse transparent proxy, or whatever you want to call it) is somewhat of an afterthought compared to the standard proxy use case. If it supports the ability to direct traffic based upon the virtual host address, then squid works - if not, I think I have to go the Apache route... I also wonder just how good Apache's mod_proxy caching is? Any thoughts? Sean -Original Message- From: Shane Hathaway [mailto:[EMAIL PROTECTED]] Sent: Monday, January 08, 2001 12:59 PM To: [EMAIL PROTECTED] Subject: Re: [Zope] Caching/http-acceleration and proxying Zope-served content [EMAIL PROTECTED] wrote: I have a question, for anyone experienced in working with Zope and caching proxies: I'm setting up a load-balanced server farm that has nodes that will run Apache and proxy (via mod_proxy) to ZEO clients running ZServer. This farm is routed (both ways) through a layer 4 load-balancing appliance, and all these boxes (both nodes and the balancer) are sitting inside a DMZ with private IP addresses. The public world will access these servers via a firewall box running transparent proxy (actually, I guess, similar to squid's http_accel mode; the semantics here are a bit tricky, as it's more of a inverse trans-proxy). Between Apache and Zope, there would be several virtual hosts, and I'd be using the SiteAccess product. It gets a bit tricky in that I need to access several different virtual hosts inside the DMZ (one for the ZEO farm, and another for a dedicated CGI-based ad server on another box) via the proxy. A more detailed (ascii art) diagram of what I am trying to do, is at http://209.132.8.98/server_ascii_art.txt My question is this: does anybody have any thoughts on the merits of Squid (http accelerator mode) versus Apache/mod_proxy in terms of caching, virtual hosts, and the like when working with Zope sites? Any big pitfalls to this kind of setup with Zope sites? I would prefer Squid since its only purpose in life is caching. It follows the "do one thing and do it well" mantra. But whatever your choice, I hope you make use of the new CacheManagement feature in Zope 2.3. It is designed to make things like this straightforward and easy. There's a recent news announcement that links to everything you need--including complete help docs! Shane ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Caching/http-acceleration and proxying Zope-served content
On Tue, 9 Jan 2001 09:31:35 +0100 (CET), Peter Sabaini [EMAIL PROTECTED] wrote: actually i use a combination of squid / apache because i need some re-writing, you could as well use squid for caching and apache for (name-based) virtual hosting. this of course introduces additional latency, but this shouldnt be a problem if your objects are fairly cacheable, ie. most content would be served out of squid anyway. That's an interesting configuration. For a while Ive been considering a solution based on longer-than-usual chains of http proxies, and a "do one thing well" principal. In my case: Apache (for rewriting and SSL) - Squid accelerator - A custom load-balancing redirector - Multiple Zopes Have you had any significant latency, or other problems? Toby Dickenson [EMAIL PROTECTED] ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Caching/http-acceleration and proxying Zope-served content
On Tue, 9 Jan 2001, Toby Dickenson wrote: :On Tue, 9 Jan 2001 09:31:35 +0100 (CET), Peter Sabaini :[EMAIL PROTECTED] wrote: : :actually i use a combination of squid / apache because i need some :re-writing, you could as well use squid for caching and apache for :(name-based) virtual hosting. this of course introduces additional :latency, but this shouldnt be a problem if your objects are fairly :cacheable, ie. most content would be served out of squid anyway. : :That's an interesting configuration. For a while Ive been considering :a solution based on longer-than-usual chains of http proxies, and a :"do one thing well" principal. In my case: : :Apache (for rewriting and SSL) : - Squid accelerator : - A custom load-balancing redirector :- Multiple Zopes : :Have you had any significant latency, or other problems? : :Toby Dickenson :[EMAIL PROTECTED] my configuration was: -- squid -- apache w/ rewriting and logging -- zserver / zope there was of course some latency added but nothing significant -- 0.5s afai can remember. and, since squid was the first stage, most content would be served of squid (and thus with no added latency) anyway. ssl was not an issue. the problem i had with zserver-only was that the most-requested pages (frontpage and index pages) were also the most expensive to render (drawing in content from diverse categories etc.) with the proxy setup, the most-requested pages would be in the cache, and little-requested pages (article views) are a) simple to render and therefore dont contribute much to load and latency and b) there's more willingness for users to wait half a second longer for a detailed view than for an index page, where they decide if they want to read anything at all (imho). i needed apache for logging and also served all static images via apache -- all those small gifs can have quite an impact of subjective load times. and since these dont change often you dont need manageability via zope. you just have to write img src="dtml-spacer_gif_path;" instead of dtml-var spacer_gif (or whatever)... ru, peter. -- _ peter sabaini, mailto: [EMAIL PROTECTED] - ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Caching/http-acceleration and proxying Zope-served content
[EMAIL PROTECTED] wrote: I have a question, for anyone experienced in working with Zope and caching proxies: I'm setting up a load-balanced server farm that has nodes that will run Apache and proxy (via mod_proxy) to ZEO clients running ZServer. This farm is routed (both ways) through a layer 4 load-balancing appliance, and all these boxes (both nodes and the balancer) are sitting inside a DMZ with private IP addresses. The public world will access these servers via a firewall box running transparent proxy (actually, I guess, similar to squid's http_accel mode; the semantics here are a bit tricky, as it's more of a inverse trans-proxy). Between Apache and Zope, there would be several virtual hosts, and I'd be using the SiteAccess product. It gets a bit tricky in that I need to access several different virtual hosts inside the DMZ (one for the ZEO farm, and another for a dedicated CGI-based ad server on another box) via the proxy. A more detailed (ascii art) diagram of what I am trying to do, is at http://209.132.8.98/server_ascii_art.txt My question is this: does anybody have any thoughts on the merits of Squid (http accelerator mode) versus Apache/mod_proxy in terms of caching, virtual hosts, and the like when working with Zope sites? Any big pitfalls to this kind of setup with Zope sites? I would prefer Squid since its only purpose in life is caching. It follows the "do one thing and do it well" mantra. But whatever your choice, I hope you make use of the new CacheManagement feature in Zope 2.3. It is designed to make things like this straightforward and easy. There's a recent news announcement that links to everything you need--including complete help docs! Shane ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
