RE: [Zope] performance tuning
My hunch would be that the reverse-proxy route is the best practice, for reasons of scalability: if you ever move to a ZEO cluster, it is highly likely that you want to put multiple ZServer instances as ZEO clients behind Squid (perhaps mod_proxy can do some sort of round-robin as well); you need a load-balancing proxy to do this. If this doesn't sell you, if you run anything that even has some mix of dynamic, semi-dynamic, and static content - this is 95% of sites - the caching aspect should. Long ago, I thought about doing Squid->Apache->Zope, and then realized that the latency of doing that much proxying is pointless (we now use Squid to proxy/balance/cache multiple ZEO clients). I can promise that, thanks to Squid, an Apache-free setup with Zope is possible, and works quite nicely. ;) Sean -----Original Message----- From: Charlie Reiman [mailto:creiman@kefta.com] Sent: Monday, September 23, 2002 1:20 PM To: Edward Muller Cc: Dirk Datzert; zope@zope.org Subject: RE: [Zope] performance tuning I doubt there'd be much difference (you can throw mod_proxy in the mix too). Relative to Zope's overhead, I don't think it even matters. But, by all means, go forth and test. I always love a good benchmark. Keep in mind that you results probably won't translate to other OSs. You might gain some real-world edge with mod_proxy which can do caching if most of your content is static. I don't know if mod_rewrite or FastCGI will help you do that.
-----Original Message----- From: Edward Muller [mailto:edwardam@interlix.com] Sent: Monday, September 23, 2002 12:06 PM To: Charlie Reiman Cc: Dirk Datzert; zope@zope.org Subject: RE: [Zope] performance tuning
He brings up another question that has been on my mind recently.
Is FastCGI faster than using Rewrite when fronting zope with Apache? Or vice versa?
On Mon, 2002-09-23 at 11:19, Charlie Reiman wrote:
Read this: http://www.zope.org/Members/richard/docs/zope_optimisation.html
There's a lot of things you can do to speed up zope and Richard talks about everyone I can think of. It doesn't cover how we got client side caching to work... I need to write that up someday. But that was more of an Apache issue than a Zope issue.
You might also upgrade your zope to 2.5.1 and maybe your apache too.
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Dirk Datzert Sent: Sunday, September 22, 2002 9:59 AM To: zope@zope.org Subject: [Zope] performance tuning
Hi,
I'm looking for perfomance tuning how-tos for:
Linux 2.4 python 2.1.3 zope 2.3.3 apache 1.3.19 with mod_proxy ZOPE caching LDAP caching ZSQL caching
Any URL would be fine.
Regards, Dirk
_______________________________________________ Zope maillist - Zope@zope.org 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 )
participants (1)
-
sean.upton@uniontrib.com