Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 47348 invoked from network); 3 Feb 2004 12:59:13 -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:59:13 -0000 Received: (qmail 35003 invoked by uid 500); 3 Feb 2004 12:59:02 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 34928 invoked by uid 500); 3 Feb 2004 12:59:02 -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 34898 invoked from network); 3 Feb 2004 12:59:02 -0000 Received: from unknown (HELO main.gmane.org) (80.91.224.249) by daedalus.apache.org with SMTP; 3 Feb 2004 12:59:02 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1Ao08n-00031h-00 for ; Tue, 03 Feb 2004 13:59:02 +0100 Received: from 195.6.79.173 ([195.6.79.173]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue Feb 3 12:59:02 2004 Received: from obillard by 195.6.79.173 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue Feb 3 12:59:02 2004 X-Injected-Via-Gmane: http://gmane.org/ To: dev@cocoon.apache.org From: Olivier Billard Subject: Re: Pools and max-objects Date: Tue, 03 Feb 2004 13:57:32 +0100 Lines: 43 Message-ID: References: <401F9382.9000003@leverageweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 195.6.79.173 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: fr-fr, fr, en, ja In-Reply-To: <401F9382.9000003@leverageweb.com> Sender: news 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 Hi Geoff, Thanks for your answer. But what's the use of this transient store, then ? For cacheable pipeline content ? On 03/02/2004 13:26, Geoff Howard wrote: > 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