I've tried both approaches... What's strange is that you'd expect every reload after the first one to take roughly the same amount of time (whether the pages are precompiled or not). However, this doesn't always seem to be the case which leads me to wonder what on earth is going on under the covers...
Cheers... Dave -----Original Message----- From: Karr, David [mailto:david.karr@;attws.com] Sent: Friday, November 01, 2002 1:49 PM To: Struts Users Mailing List Subject: RE: WebLogic/Struts/JSP performance woes... Is your page precompiled? Are you doing the timing test on your second display of the page? The first display of a non-precompiled JSP will take much longer, as it has to generate and compile the servlet class. > -----Original Message----- > From: Davide Bruzzone [mailto:Davide.Bruzzone@;ngt.com] > Sent: Friday, November 01, 2002 12:43 PM > > I have a page that, for test purposes, is generating a 1760 > row table (Not a > gigantic table by any stretch of the imagination). Although I > don't expect > our data sets to be this big all the time, I need to make the > application > responsive (i.e. If it starts displaying rows immediately - > while its still > spitting out other rows - that's fine. What's unacceptable is if the > application takes a while to do whatever its doing, and > doesn't generate any > output until its done, leaving the user with a blank page > while they wait). -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
