I have the same problems. I have a massive tapestry app and it appears at least 45% of the time is spent in OGNL (vs. 30% in database/datamapping code). I'm using 3.03 as well because I have similar deadlines to meet and rewrote a bit too much of 3.0 last year to support some of the features that are now showing up in 4.0. It looks like I might be forced to switch to 4.0 quicker than I thought.
I believe the time to render a template should be comparable to the time to render the same content without a template and it is definatly not that way in 3.03. Parameter binding and ognl evaluation are to expensive and this is having a serious effect on performance. I'm glad to see that work has been done and is being done to resolve this. Kris -------------------- m2f -------------------- Sent from www.TapestryForums.com Read this topic online here: <<topic_link>> http://www.tapestryforums.com/viewtopic.php?p=11198#11198 -------------------- m2f --------------------
