Yup, we looked at overall size of the JSP as well, and the association with performance was definitely number of bm/bw tags within a single JSP rather than overall JSP size. We even tried editing the generated servlet code and adding big unused methods to see if the problem had to do with generated servlet file size. That would kind've made sense, but was a negative. I believe we also tried a tag that just did a sysout rather than any kind of memory lookup (hashtable or properties file) and found that this performance quirk in the sun vm did not appear in that case.
We could never pin down a why, it seemed that the sun 1.3 vm just ran like a snail with a lot of bm or bw tags in a single page, so we stopped doing that ;-). Same number of tags split up into multiple JSPs, or a few tags called the same number of times via a loop - OK performance. It is very true also that splitting them up into smaller bites makes them more readable and maintainable, so it was a good solution all around. It's just that you are always nervous when you fix a problem and don't know the why of it ;-). Jimbo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
