That's consistent with numbers I've found in migrating one app from 1.3 to 2.0. I've always held out hope that this was just something that optimization could take care of. In the meantime, my performance isn't terrible, but it doesn't fly like it did in 1.3, either. Here's hoping the optimization works! I'd offer help except I'm terrible at profiling. If you identify things that profiling indicates need work and need someone to handle some grunt work, let me know. I'm eager to get my old performance back.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrick Lightbody Sent: Thursday, November 13, 2003 7:43 PM To: WebWork Subject: [OS-webwork] EL Performance Between 1.3 and 2.0 I've finished the backwards support for the 1.3 EL and have migrated the first mini-app over from 1.3 to 2.0 with almost zero effort: the monthlist test. I wanted to share the performance numbers: * WebWork 1.3 scored 80ms * WebWork 2.0 w/ old EL support scored 550ms * WebWork 2.0 w/ new EL scored 300ms I'm not really worried about the old EL support, as I can speed up in a few areas (especially by caching the Pattern objects used in the regex logic). However, the 3X - 4X speed decrease is certainly not good. I expect the new EL to be a bit slower given new features added (type conversion requires evaluation tracing). My target is no more than a 10% slowdown. Anyway, I'll be working on this for the next couple of days. -Pat ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
