Joe Barefoot schrieb:
> Since each JSP compiles down to a single method call in the
generated source
> class, and (depending on how the JSP compiler generates Java
source) each
> custom tag could potentially have its own try/catch block as well
as several
> local variables, the more 'stuff' you have on a single page
correlates to
> the amount of stack memory required for the local scope of the
method call.
I tried to track down the problem (with the unsplitted page) with
System.out.println statements. With this procedure I discovered that
most of the time (4 sec) is consumed in one piece (=between two source
code lines) but not always at the same source code lines. I assumed a
memory allocation problem but increasing the page buffer to 100kb
didn't help.
It looks like Tomcat is "taking a break" for 4 sec before delivering
the next content. During this break CPU load raises up to 100%.
Do you know under which circumstances this or similar behaviour can
occur with Tomcat?
Regards
gus
> -----Original Message-----
> From: gus [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, September 07, 2002 7:15 AM
> To: [EMAIL PROTECTED]
> Subject: Improving performance by splitting JSP?
>
>
> Hi!
>
> I had a performance problem in my struts application where one JSP
> page took about 5 secs to display (Tomcat 4.0.4, Struts 1.1b1, Win2k,
> PIII 500, 512Mb). The page uses struts taglibs (bean, logic, html) and
> is nearly 300 lines long.
>
> I tried to track down the problem but with no luck. Finally I split
> the page into 3 parts using <jsp:include ...> and now the whole page
> loads 5 times faster.
>
> Does anybody made the same experience and/or has an explanation for
> that behaviour?
>
> Regards
> gus
>
>
>
> --
> 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]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
