I'm actually performing a series of benchmarks that are close to what you describe, though the pages are complex, in that JSTL is used to markup logic. the test pages are highly dynamic and use includes extensively to break pieces into logical chunks.
once I am done I will post the results. peter lin [EMAIL PROTECTED] wrote: > The most usefull tools are OptimizeIt and ab. > > Simple pages would help much better then complex pages - first find > out what's the overhead of executin a simple JSP page, with no tags, > compare it with the equivalent servlet ( HelloWorld ), and find out > what's wrong. > > Then use a simple hello world Tag, compare it with the equivalent > servlet ( or JSP not using tags ), and find what's wrong. > > Same for a simple iteration tag, compared with a scriptlet > > If you solve those simple problems, and get the tag version > in a reasonable limit, I think we'll all be very happy ( 30% slower > would be acceptable for me, even 1/2 the speed of the equivalent > scriptlet ). > > Going after 'real life applications' when the simple hello world tag, > or a simple empty jsp page has a clear performance penalty would be a > waste of time. > > ( all that with a reasonable load - I sugest 80 concurent requests ) > > Costin > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
