Also using tomcat for any kind of performance test like this one would be rather...silly. It'd be like using jboss to prove that ejbs suck. Of COURSE a given tech will suck if you choose a braindead impl. In the case of velocity vs jsp, I'd be inclined to discard any tests on servers other than orion/resin. For one thing, I'm pretty sure that the developers of those containers would very quickly scramble to speed up their jsp impls if a good example can prove that it's slower than using velocity.
On Thursday, March 13, 2003, at 12:50 PM, Scott Farquhar wrote:
Hani,
It is fairly simple to test - given that CVS HEAD has tags based on either velocity or jsp.
There are two sources of potential slowness with jsp: - parsing & rendering overhead - rd.include() overhead.
From my experience both of the above can be reduced by using velocity. Tomcat (until recently) was very slow doing an rd.include(), which is the way that the webwork tags work (including the template).
However, the currently commited velocity tags (1.3/CVS HEAD) still use the rd.include(), and the velocity servlet to serve the content. They still serve the page much faster than JSP (on almost all containers), so there must some overhead in the parsing & rendering also.
Overall, JSP compilation and servlet containers are improving, and one day Tomcat & Jetty will be much closer to Orion/Resin. However, if you are looking for a constant (fast) time across containers, then you choose velocity, as it is a known variable.
That given, there are a lot of things about velocity that shit me, such as #foreach(Map) iterating across the keyset and not the entryset, and few ugly parsing issue that make it hard to do webwork's funky loosely-typed syntax easily.
Cheers, Scott
Hani Suleiman wrote:Alright, so based on the feedback so far, the consensus seems to be:
webwork jsp UI tags are much slower than velocity equivalents. So the culprit seems to be the webwork UI tags, not jsp itself.
On Thursday, March 13, 2003, at 12:13 PM, boxed wrote:-------------------------------------------------------scriptlets will probably be almost as fast, I'm guessing. Tags could be
much
slower, since the way that containers handle tags is different for each
container.
As I've understood it the tag overhead itself isn't really that big of an
issue, the tags ARE reused after all. The JSP include the webwork UI tags
use, however, is HORRIBLY slow. Velocity includes are practically no time
whatsoever.
Anders Hovmöller [EMAIL PROTECTED] http://boxed.killingar.net
------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
--
ATLASSIAN - http://www.atlassian.com Expert J2EE Software, Services and Support ------------------------------------------------------- Need a simple, powerful way to track and manage issues? Try JIRA - http://www.atlassian.com/software/jira
------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
