On Thursday, January 23, 2003, at 07:20 PM, Bill Lynch wrote:
Peter,Just an FYI, a more scientific way to do this would be something like the following:The Methodology --------------- Look at the clock by my desk and count how many whole seconds elapse before the page renders. Do not count the initial page compile in the data. Repeat 10 times and average the results.
long time = System.currentTimeMillis();
// Code here you want to profile
time = System.currentTimeMillis() - time;
System.err.println("That took " + time + " milliseconds.");
Also, another advantage to this is you could embed it in the JSP page so that would truly measure the speed of the WW UI code and not your EJB layer or the browser rendering time.
Cheers,
--Bill
-------------------------------------------------------
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
------------------------------------------------------- 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
