On Tue, Mar 19, 2002 at 12:07:12PM -0500, Adam Manock wrote:
>
> >Interesting. One complication with that scheme is that ther is no
> >convenient place to put caching. If it goes between Pen and Zope, you
> >need many instances of your cache. If it goes between Pen and the
> >clients, Pen's clien
>Interesting. One complication with that scheme is that ther is no
>convenient place to put caching. If it goes between Pen and Zope, you
>need many instances of your cache. If it goes between Pen and the
>clients, Pen's client-clustering is defeated because it sees only one
>client.
Postgresql
On Tue, 19 Mar 2002 11:02:27 -0500, Shane Hathaway <[EMAIL PROTECTED]>
wrote:
>First, you'll need a load balancer. Here is a lightweight one that
>sounds like a good match for Zope, although I haven't tried it:
>
>http://siag.nu/pen/
>
>It actually tries to match clients with servers, which sho
Anthony Baxter wrote:
"Adrian Hungate" wrote
>>moved to a different thread or earlier, before the fork, so that we could
>>simply kill senile threads without killing the entire shooting match?
>>
>
> unfortunately apache does this with seperate processes, not threads.
>
> memory corrupt
ay, March 19, 2002 8:31 AM
Subject: Re: [Zope-dev] A thought for 2.6 about various leaks and memory
problems
On Tue, 19 Mar 2002 08:08:47 -, "Adrian Hungate"
<[EMAIL PROTECTED]> wrote:
>For the last few weeks (And maybe longer) I have been seeing lots of
>messages about zop
On Tue, 19 Mar 2002 08:08:47 -, "Adrian Hungate"
<[EMAIL PROTECTED]> wrote:
>For the last few weeks (And maybe longer) I have been seeing lots of
>messages about zope leaking, the gc crashing and generally, Zope going
>senile after long runtimes or lots of requests. This was (And I believe
>s
>>> "Adrian Hungate" wrote
> moved to a different thread or earlier, before the fork, so that we could
> simply kill senile threads without killing the entire shooting match?
unfortunately apache does this with seperate processes, not threads.
memory corruption and leaks aren't solved by offing
For the last few weeks (And maybe longer) I have been seeing lots of
messages about zope leaking, the gc crashing and generally, Zope going
senile after long runtimes or lots of requests. This was (And I believe
still is) a problem for Apache, which they solved by having threads only
live for a ce
