Well, I'm probably not the guy to ask, but I've forwarded this to the Zope mailing list, maybe some folks there can give you an idea of what to expect in the way of scalability... -----Original Message----- From: Bill_Seitz@mail.medscape.com [mailto:Bill_Seitz@mail.medscape.com] Sent: Tuesday, October 12, 1999 5:54 PM To: Chris McDonough Subject: RE: zope vs siteserver Feel free to forward. I'm just learning Python a bit. I'm intrigued by Zope, but wary about getting wrapped up in a platform that won't meet my future scale needs. A key aspect of performance, in my opinion, is handling of SQL calls, since that's what most dynamic sites are going to use as a back end. So a "select * from helloWorld" kind of page would be nice.... Chris McDonough <chris@iqgroup.com> on 10/12/99 05:40:46 PM To: Bill Seitz/Medscape@Medscape cc: Subject: RE: zope vs siteserver hmmm... i read somewhere (it was mod_perl benchmarking, I think) that a "hello world" application written in ASP/VBscript performed at about 9 requests/sec. mod_perl came in at about 53 requests/sec. static HTML came in at about 1800 requests/sec. i also read somewhere that a good rule of thumb average for Zope serving is about 16 req/second. would you mind if I forwarded this question to the zope list and possibly to the site server usenet group? -----Original Message----- From: Bill_Seitz@mail.medscape.com [mailto:Bill_Seitz@mail.medscape.com] Sent: Tuesday, October 12, 1999 5:42 PM To: mcdonc@iqgroup.com Subject: zope vs siteserver How about scalability/performance as a criterion. Very hard to measure, of course. Would need to define some sort of generic "representative" site, using a mix of features, then throw some load at it and see how it performs.