Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3C331F2B.4070809@apache.org>
Date: Wed, 02 Jan 2002 09:54:35 -0500
From: Berin Loritsch <bloritsch@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:0.9.7) Gecko/20011221
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: Cocoon scalability continued
References: <GMEBIBHGAOFGJCDPJANDKEOFDFAA.cziegeler@s-und-n.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Carsten Ziegeler wrote:

> Michael Homeijer wrote:
> 
>>Hi,
>>
>>This mail is a follow-up to the following mails:
>>
>>(Cocoon 2 RC2 performance disappointment).
>>http://www.mail-archive.com/cocoon-dev@xml.apache.org/msg06455.html
>>
>>and
>>
>>(Cocoon 2.0 Scalability Disappointment)
>>http://www.mail-archive.com/cocoon-dev@xml.apache.org/msg06751.html
>>
>>In the last weeks we observed that Cocoon performance and scalability are
>>greatly influenced by a number of factors, to name a few:
>>- Complexity of pipelines (slows down pipeline composition)
>>  > Stefano mentioned to me that entire pipelines can be pooled.
>>  > Can anybody give me some directions on how to accomplish this?
>>
> Do you mean pooled? AFAIK this is not possible. Complete pipelines can
> be cached but not pooled.


It would be possible with a different implementation of Pipeline and useage
model for the pipelines.  IMO, the development of this change would be worth
it.

The change does not favor the current method of generating pipelines, but then
again, it would have to be rewritten.


-- 

"They that give up essential liberty to obtain a little temporary safety
  deserve neither liberty nor safety."
                 - Benjamin Franklin


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org