> From: Peter Royal [mailto:[EMAIL PROTECTED]] > > On Saturday 27 July 2002 10:15 am, Vadim Gritsenko wrote: > > About complexity itself: I'm referring to this particular change in > > DefaultComponentFactory: > > > > http://cvs.apache.org/viewcvs.cgi/jakarta-avalon-excalibur/src/java/org/ > > apache/avalon/excalibur/component/Attic/DefaultComponentFactory.java.dif > > f?r1=1.10&r2=1.11&diff_format=h > > > > Addition of > > > > private final Collection m_unreleased = new ArrayList(); > > > > slows down Cocoon from 8% (dynamic page) to something around 20% (page > > from cache). > > Is it slower on component creation from the DefaultComponentFactory or upon > general ComponentManager.lookup() calls with the new added proxy?
Pete, Component creation isn't bottleneck, lookup/release time is important. When Cocoon works from cache, it does essentially just couple of things: 1. Lookups *and* releases tons of components (ok, not tons, just 5-15), 2. Verifies validity, 3. Sends response back (sometimes - from in-memory cache). These three tasks by my estimates (and some old profilings with optimizeit) split whole 100% processing time on three slices (approximately): 20% - 70% - 10%. Actually, release is slower then lookup, because it invokes iterating through all lists in all proxies, which takes more time with growing complexity of the site (aggregations etc). When response is not from cache, of course most of the time is spent in XSP generation and XSLT processing, and Avalon's slice decreases to 8% (simple.xsp) and below. Regards, Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
