poolable interface / performance

[Jorg Heymans <jh...@domek.be>]

Say i define a custom transform like this

     <map:transformer name="mytransformer"
     	src="mytransformer"
		pool-max="200"
		pool-min="20"
		pool-grow="10"/>	

In order for these pool settings to take effect, do I need to implement 
the poolable marker interface then or does this happen by default?
Can anyone comment on the performance of using pooled components vs 
non-pooled?


Jorg

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

Re: poolable interface / performance

["Rui Alberto L. Gonçalves" <ru...@ptinovacao.pt>]

On Thu, 2003-12-11 at 15:32, Jorg Heymans wrote:
> Say i define a custom transform like this
> 
>      <map:transformer name="mytransformer"
>      	src="mytransformer"
> 		pool-max="200"
> 		pool-min="20"
> 		pool-grow="10"/>	
> 
> In order for these pool settings to take effect, do I need to implement 
> the poolable marker interface then or does this happen by default?
If you want that the component manager to treat your component
as a poolable one, it must be marked as poolable and the component
manager will do all the work for you!
Since your transformer is probably an extension to AbstractTransformer
 wich is already marked as poolable, you don't have to do anything.


> Can anyone comment on the performance of using pooled components vs 
> non-pooled?
> 
> 
> Jorg
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
-- 
Rui Alberto L. Gonçalves <ru...@ptinovacao.pt>
PT Inovação


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