From dev-return-54962-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Tue Feb 03 12:27:44 2004 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 31083 invoked from network); 3 Feb 2004 12:27:44 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Feb 2004 12:27:44 -0000 Received: (qmail 23644 invoked by uid 500); 3 Feb 2004 12:27:36 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 23598 invoked by uid 500); 3 Feb 2004 12:27:36 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 23575 invoked from network); 3 Feb 2004 12:27:36 -0000 Received: from unknown (HELO host.leverageweb.com) (64.91.254.192) by daedalus.apache.org with SMTP; 3 Feb 2004 12:27:36 -0000 Received: from va-leesburg-cmts5c-90.chvlva.adelphia.net ([67.21.159.90] helo=leverageweb.com) by host.leverageweb.com with esmtp (Exim 4.24) id 1AnztX-00036b-26 for dev@cocoon.apache.org; Tue, 03 Feb 2004 07:43:11 -0500 Message-ID: <401F9382.9000003@leverageweb.com> Date: Tue, 03 Feb 2004 07:26:42 -0500 From: Geoff Howard User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Pools and max-objects References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.leverageweb.com X-AntiAbuse: Original Domain - cocoon.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - leverageweb.com X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Olivier Billard wrote: > Hi cocooners ! > > Interaction between max-objects defined in cocoon.xconf and the pool-max > of poolable components is not very clear for me. Thanks for bringing me > the light :). > > Is max-objects the great max of object instances that can live in > cocoon, ignoring the pool-max defined for each object ? > In that case for exemple, if I have 5 poolable objects with pool-max set > to 32 and max-objects set to 100, will I never fill all the pools to max > ? If 100 instances of my objects are created, i'll never get others ? > > I've read in the wiki [1] that the max-objects must be set from 4000 to > 8000 in production, that i think well, is more correct than the 100 > defaut... > > But with a minimal build (datasource, portal and 1 or 2 more blocks), > there is at least 5 poolable objects with pool-max set to 32, that could > (on heavy load i agree) create up to 160 objects, but with max-objects > set to 100, that could never happen, no ? > > > Thanks for your answers ! > > [1] : http://wiki.cocoondev.org/Wiki.jsp?page=CocoonPerformance From that page: "Make sure you set the "maxobjects" (cocoon.xconf) of the transient-store...". Transient store is totally unrelated to the component instance pools, so there is no interaction between the numbers. Geoff