if you do a search on taglibs-user for 2002, you'll lots of benchmarks I ran using
JSTL. The long and short of it is this.
1. JSP tags use quite a bit more memory than scriptlet (i.e. pure java embedded in
jsp). Many people consider scriptlet evil.
2. if you're using more than 150 tags per page, you should consider turning on tag
pooling if you're using tomcat. If you're not using tomcat, see if your webserver
supports tag pooling.
3. are your beans efficient. things like doing search may be cpu/time intensive.
4. what is the expected concurrent load?
tomcat5 just went stable and it supports page level tag pooling. If you can, run
OptimizeIt on your pages to see exactly why it's not performing well. JSTL may not be
the cause, but you won't know until you get real data.
peter
Jim Kennedy <[EMAIL PROTECTED]> wrote:
I've been reading some developers comments that the JSTL does not perform very well.
I'm am experiencing poor performance that I attribute to the use of the JSTL. Here is
something typical I do:
------------------------------------------------------
[input] " name="">
Description: [input] " ${search[?des_key?]}?>" size="20" class="textbox">
Model Number: [input] " ${search[?mn_key?]}?>" size="20" class="textbox">
Serial Number: [input] " ${search[?sn_key?]}?>" size="20" class="textbox">
PO Number: [input] " ${search[?po_key?]}?>" size="30" class="textbox">
Location: "> Select a location " test="${location.id==search['asset_locationcode']}"
SELECTED >
[input]
[input]
---------------------------------------------------------------
Is there something I'm doing in the code that I could avoid to enhance the
performance. This is only a code fragment. Assume that variables are defined in
advance.
---------------------------------
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
