> From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] > > > From: Peter Royal [mailto:[EMAIL PROTECTED]] > 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).
With Fortress, all release() operations are done asyncronously. That means that we can have expensive decisions that need to be done without affecting the critical path of execution. > 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. It can still be faster. I haven't been able to attempt the switch to Fortress yet.... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
