I guess I'm confused. Everything that *could* be cached *was* cached. And no, I don't run a caching server or a proxy server or anything else in front of Zope. I'm a writer, not a programmer. The /. piece hit about 1:00 AM. By 1:01 AM Zope had folded like a cheap suit. It's still going down about every 40 minutes or so. Now remember, my outbound bandwidth is limited to 512Kb. Am I correct in my understanding that Zope can't handle even 512Kb of demand without some technical doohickey in front of it so it doesn't fall down? No offense intended, but I think two internal Squishdot pages meet the definition of pretty dang simple. And why does it fall over anyway? This just doesn't make any sense to me. I can see it getting slow and timing out, but giving up completely and just bailing? What's that about? Explain it to me like I'm an intelligent, non-technical friend. Thanks. -- Michael Fraase ARTS & FARCES LLC mfraase@farces.com www.farces.com PGP Fingerprint: 3D85 F3F4 9E65 4949 176A 260C CB47 190D C864 9A96
-----Original Message----- From: Chris McDonough [mailto:chrism@zope.com] Sent: Tuesday, November 20, 2001 2:38 PM To: Chris Withers Cc: mfraase@farces.com; zope@zope.org Subject: Re: [Zope] Urgent help needed: Zope falls over under moderate load
Hurm... so Zope's no good if you want to build a scalable _and_ dynamic site?
surely that's a little worrying?
Not really. Zope depends on caching and cannot survive a high transaction rate without it unless your site is very very very simple. Usually, if you don't cache or serve only static content, you can't running a high-volume site using Zope or mod_perl or ASP or whatever-else; it's as simple as that.
But you knew that.
- C