Hi Geoff,
Thanks for your answer. But what's the use of this transient store, then ? For cacheable pipeline content ?
Yes, and some other components are using it for cacheable by-products I think, but not for component instances which the pool settings are about.
Geoff
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
