I agree with Nikola- I would run an execution plan on the query in question ..and do so locally (vs a DB 500 miles distant) specifically note the access (do you see any FTS?) and time deltas (more than 30 sec to see results merits tuning( Note -the attenuated time delta and -faster access via hinted HASH/NL Joins etc..
HTH Martin -- ********************************************************************* This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. ----- Original Message ----- From: "Nikola Milutinovic" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Wednesday, July 19, 2006 3:01 AM Subject: Re: Intermediate write in JSP >> I had a similar issue in the past that I overcome by having the servlet >> start a separate thread that was producing the report, >> And a jsp page refreshing every 10 seconds or so checking for completion. > > > That is, of course, the asynchronous application design. Sometimes it is > necessary, but it does bring a question. What is being so slow? Sending the > amount of data you're sending is not slower than it can be. My guess is that > DB is taking a rather long time to complete the query. I would not blame the > network, because the Net connection between DB and TC should be at least as > fast as the one between TC and your client. > > So, the original poster might wanna take a look at the DB for speeding it up. > It might not be possible, though. > > Nix. > > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
