On Fri, 1 Nov 2002, Davide Bruzzone wrote: > Date: Fri, 1 Nov 2002 13:43:26 -0700 > From: Davide Bruzzone <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > Subject: WebLogic/Struts/JSP performance woes... > > Greetings all... > > I'd like to try to find out if anyone else out there is using WebLogic > (We're using version 6.1 SP2) with Struts and/or just JSPs that might have > some performance tips that they might be able to share... > > Here's what's happening: > > 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). >
There are at least a couple of things going on here to watch out for (neither of which Struts can really help you much with): * How fast does your database actually retrieve the data? Because you found that switching to scriptlets didn't help a lot, I suspect that this is going to be the ultimate limit to how fast your page can be rendered (although you can certainly improve the "perceived" response time by beginning visual rendering before the response has been completed. * What browser are you testing with? If it's Netscape 4.x, you're going to be in a world of hurt -- besides being very slow in the first place, Netscape 4.x won't start rendering an HTML <table> until the </table> element has been received. Try a newer browser, or divide up your huge table into separate shorter tables (say, every 50 rows or so). My stronger advice, though, is that a 1760 row table is not particularly usable even if it rendered instantly. I'd suggest looking at strategies that let the user refine what they are searching for more carefully, and/or set things up to scroll through multiple short result pages (like a search engine does). Craig -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
