Even though this is for WW, almost all of it is applicable to Struts 2.
This is a key phrase. There are a lot of very successful WW deployments out there, with the same performance levels. We really need to setup our own benchmarks, so that we can run them with the templates deployed. I'd love to do this myself, but I'm totally time-deprived right now.
Eventually we'll move this to S2 and update it, but so few people are using Struts 2 right now, I think this is adequate.
That's going to change quite quickly. Even though we're still in beta, people are already posting jobs for S2. Even though the benchmarks might not tell the whole story, narrowing the cycles would make it easier for more people to adopt S2 (And hopefully some of those will lend us a hand. Even with the merge, we still don't have more active committers than we had a year ago.) -Ted. On 1/17/07, Tom Schneider <[EMAIL PROTECTED]> wrote:
The performance of OGNL is not nearly as bad as we had originally thought. I've been doing some performance testing in Webwork (which S2 is based on) this week and most of the OGNL calls are not measurable. (<1ms) The biggest issue I've had is making sure freemarker templates are getting cached properly. See http://wiki.opensymphony.com/display/WW/Performance+Tuning for details. (I'll be adding some explanations to what phil wrote later this week) Even though this is for WW, almost all of it is applicable to Struts 2. Eventually we'll move this to S2 and update it, but so few people are using Struts 2 right now, I think this is adequate. Tom
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
