Still working on the memoryu, but here are the results of running the ContainerProfile test before and after the patch was added.
Before: --- Running org.apache.avalon.excalibur.system.test.ContainerProfile DEBUG 10142 [ ] (): added new LogTargetFactory of type file DEBUG 10142 [ ] (): added new LogTarget of id root DEBUG 10142 [ ] (): added logger for category test.test INFO 10142 [test ] (): Test Case: ECM_ContainerManager_StartTime INFO 10142 [test ] (): ECM time = 1522ms. INFO 10142 [test ] (): ContainerManager time = 1412ms. INFO 10142 [test ] (): => ContainerManager is 1.07 X as fast as ExcaliburComponentManager on init. INFO 10142 [test ] (): => ExcaliburComponentManager is 0.92 X as fast as ContainerManager on init. INFO 10142 [test ] (): Test Case: Test Case: ECM_ContainerManager_UseageTime INFO 10142 [test ] (): AbstractContainer$ContainerComponentManager time = 4647ms. to use 50000 calls on 3 components. INFO 10142 [test ] (): ExcaliburComponentManager time = 259493ms. to use 50000 calls on 3 components. INFO 10142 [test ] (): => AbstractContainer$ContainerComponentManager is 55.84 X as fast as ExcaliburComponentManager. INFO 10142 [test ] (): => ExcaliburComponentManager is 0.01 X as fast as AbstractContainer$ContainerComponentManager. INFO 10142 [test ] (): Test Case: ECM_ContainerManager_KillTime INFO 10142 [test ] (): ECM time = 10ms. INFO 10142 [test ] (): ContainerManager time = 671ms. INFO 10142 [test ] (): => ContainerManager is 0.01 X as fast as ExcaliburComponentManager on dispose. INFO 10142 [test ] (): => ExcaliburComponentManager is 67.1 X as fast as ContainerManager on dispose. Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 269.979 sec Testsuite: org.apache.avalon.excalibur.system.test.ContainerProfile Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 269.979 sec Testcase: testCompare_ECM_ContainerManager_UseageTime took 269.979 sec --- After --- Running org.apache.avalon.excalibur.system.test.ContainerProfile DEBUG 10142 [ ] (): added new LogTargetFactory of type file DEBUG 10142 [ ] (): added new LogTarget of id root DEBUG 10142 [ ] (): added logger for category test.test INFO 10142 [test ] (): Test Case: ECM_ContainerManager_StartTime INFO 10142 [test ] (): ECM time = 2353ms. INFO 10142 [test ] (): ContainerManager time = 1402ms. INFO 10142 [test ] (): => ContainerManager is 1.67 X as fast as ExcaliburComponentManager on init. INFO 10142 [test ] (): => ExcaliburComponentManager is 0.59 X as fast as ContainerManager on init. INFO 10142 [test ] (): Test Case: Test Case: ECM_ContainerManager_UseageTime INFO 10142 [test ] (): AbstractContainer$ContainerComponentManager time = 4046ms. to use 50000 calls on 3 components. INFO 10142 [test ] (): ExcaliburComponentManager time = 213668ms. to use 50000 calls on 3 components. INFO 10142 [test ] (): => AbstractContainer$ContainerComponentManager is 52.8 X as fast as ExcaliburComponentManager. INFO 10142 [test ] (): => ExcaliburComponentManager is 0.01 X as fast as AbstractContainer$ContainerComponentManager. INFO 10142 [test ] (): Test Case: ECM_ContainerManager_KillTime INFO 10142 [test ] (): ECM time = 10ms. INFO 10142 [test ] (): ContainerManager time = 691ms. INFO 10142 [test ] (): => ContainerManager is 0.01 X as fast as ExcaliburComponentManager on dispose. INFO 10142 [test ] (): => ExcaliburComponentManager is 69.1 X as fast as ContainerManager on dispose. Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 229.64 sec Testsuite: org.apache.avalon.excalibur.system.test.ContainerProfile Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 229.64 sec Testcase: testCompare_ECM_ContainerManager_UseageTime took 229.64 sec --- While startup time slowed down a bit, usage time got slightly better. The new ContainerManager is a big improvement in speed though. (kudos) You might want to try running a modified version of the ExcaliburComponentManagerTestCase on it and see how it handles the dispose order problems that the patch fixed. I was able to reproduce memory leak. Still looking into how to fix it. Leif Berin Loritsch wrote: > There was a memory leak introduced in the ECM patches last night. > Yesterday, the test kept a constant memory consumption (somewhere > around 16 MB for the ECM portion of the test). To day, the JVM > memory usage grows constantly with each lookup/release cycle, > starting around 15 MB, cand growing to 27 MB. > > Could someone track that down? > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
