Patrick Lightbody wrote:
As I may have mentioned we are basing our SiteVision CMS/portal product entirely on WebWork/Velocity. Based on benchmarks I've done the above sounds about right (e.g. an average page with about 10 Velocity portlets render in ~50ms, even under high load). Velocity is incredibly fast, and scales very well.Small followup to that:In a result JSP (success.jsp in the example app for WW 2.0) I placed 50 calls of either: <ww:textfield .../> or <ww:vmtextfield ../> Average response time when using the JSP-based components: 162ms Average response time when using the velocity-based components: 38ms That's a performance boost of 4X. Also, I don't have a test for this, but it "feels" like velocity also scales more. Here's my less scientific test: Using the JSP-based example from above, I held down "reload" so that about 40 http requests were sent in. The time for the final 20 requesst to be handled took on average 40 -seconds-. When using velocity under the same test, the final 20 requests took on average 1.4 seconds. That's a scalability factor of about 30X!
Which is why I proposed that we switch to it for the UI tags. I'm happy to see that your tests verify this idea :-)
/Rickard
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
