Daniel, >Have you tried looking at the Query that you using. 1760 rows from a >database may some time to transfer and query up. You can sometimes shave >seconds from a query by just changing the order of the FROM clause and WHERE >conditions.
The query runs in under a second, and the data is available for use in about 3 - 4 seconds. >Since you said that only sometimes that the users need to see all the rows, >why do you not implement a paging by default. Then have an option to see >all rows. Interesting idea. In the end, depending on what the users say, we'll probably end up implementing a combination of some of the things that we've tried, and many of the things that have been suggested on this list. Cheers... Dave ----- Original Message ----- From: "Phil Steitz" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Saturday, November 02, 2002 12:34 PM Subject: Re: WebLogic/Struts/JSP performance woes... > David, > > Have you considered running some tests with Jmeter or some other testing > tool that can tell you exactly how long it takes to deliver the HTML? > This would enable you to determine whether the problem is on the server > side or in the browser rendering. -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
