Gentlemen, We're in the midst of evaluating WebWork for a redesign of our site, and have cobbled together a simple demo that consists of a form that takes either an integer or a string, an action that loads an object based on the input using Hibernate, and a page that displays the properties of the loaded results.
When we have issued the same request many times to warm up the JVM JIT and ensure that the object is in Hibernate's cache, we're still seeing round-trip results on the order of ~600 milliseconds under load of 10 simultaneous threads. When we examine the logs, we find that the time from findValue() of the first property on the page to the last is ~411 milliseconds, for 57 uses of the property tag. The usage form is quite simple: <ww:property value="product"> <ww:property value="serialNumber"/> <ww:property value="quantity"/> ... </ww:property> It's also interesting to note that on a previous, single-threaded run, I saw at least one timing from first findValue() to last of only 45 milliseconds. So it would appear, at first blush, that ValueStack.findValue() suffers from nasty thread contention. I wonder if anyone on the team could comment, and in particular, what the status of some of the performance improvements to ValueStack.findValue() are? Is there now a branch with these improvements, or can the developer who implemented/is implementing them please tell us how to integrate them? 45 milliseconds for 57 findValue()s is acceptable; 411 is not. Any advice as to how to proceed would be most welcome. Many thanks and best regards, Paul Snively ------------------------------------------------------- This SF.net email is sponsored by: The Sourceforge Network Survey Take Our Survey and You Could Win a $500 Gift Certificate! http://ugamsolutions.com/psurvey/osdn/SourceForge/index_sourceforge.htm _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
