Details
-
Test
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
2.2
-
None
-
None
-
Patch available
Description
This is a patch that makes the pooling of components/beans optional: by setting this in the applicationContext.xml
<!-- Activate Avalon Bridge -->
<avalon:bridge pooling="false"/>
it is possible to turn off pooling completely. The idea is to start testing performance differences between pooling and non-pooling. The default value for the "pooling" option is true, so existing configurations without the attribute set will behave as before when this patch is applied.
Pooling was introduced back then when creating a new object in Java was slow and re-using of existing objects was faster. Since Java 1.4 this is no longer the case, creating new objects is said to be even faster than malloc() in C. Because pooling needs a recycle() method (to reset internal stuff before reuse) and more calls, including some AOP and Proxy class stuff to add pooling, it is worth to check what is faster nowadays.
One thing that always annoys me during debugging is that the AOP stuff adds like 4-5 additional calls when accessing a pooled component in the stacktrace - code that you cannot step into, because it has no java source. Removing pooling completely would make the Cocoon architecture (especially the runtime architecture) much simpler.
My idea is that Cocoon users can test the performance difference on their various systems to get actual results. WDYT?
<!-- Activate Avalon Bridge -->
<avalon:bridge pooling="false"/>
it is possible to turn off pooling completely. The idea is to start testing performance differences between pooling and non-pooling. The default value for the "pooling" option is true, so existing configurations without the attribute set will behave as before when this patch is applied.
Pooling was introduced back then when creating a new object in Java was slow and re-using of existing objects was faster. Since Java 1.4 this is no longer the case, creating new objects is said to be even faster than malloc() in C. Because pooling needs a recycle() method (to reset internal stuff before reuse) and more calls, including some AOP and Proxy class stuff to add pooling, it is worth to check what is faster nowadays.
One thing that always annoys me during debugging is that the AOP stuff adds like 4-5 additional calls when accessing a pooled component in the stacktrace - code that you cannot step into, because it has no java source. Removing pooling completely would make the Cocoon architecture (especially the runtime architecture) much simpler.
My idea is that Cocoon users can test the performance difference on their various systems to get actual results. WDYT?