We've inherited an web app written by an external company, using
IIS/ASP. We're after any pointers that more experienced folks can give,
and would prefer to fix up in house as the external company wants more
moolah to fix anything.

The site is currently low trafiic, no more than a couple of sessions an
hour (if that). We're hosting it in the offices at the moment, the login
and registration side of this site needs to integrate with our main site
which we've just moved to an external ISP. We have had to change the
Oracle DB to use the DB at the ISP, rather than our in-house DB to make
things work smoothly.

Since we made the change this morning, the site's been *really* slow for
the first page in any session. Subsequent browing is fine - it's just
the first page that's bad. I'm assuming that this is because the
connection to Oracle is being made at the same time the session is being
created, and that hangs around as long as the session is live on the
server.

We've had a play with the ODBC connection pooling, it was already
enabled with a 60 second timeout. We've tried to increase this value to
increase the chance of existing DB connections still being around, but
it doesn't seem to have made any difference.

Is there something else easy we can try - or will it need a code
overhaul?

Sorry to be so vage, just looking for some pointers if possible?
	
  _____  

GMG Regional Digital is part of the Guardian Media Group plc, Official
Media Sponsor of the Manchester 2002 Commonwealth Games.




CONFIDENTIALITY NOTICE. The information contained in this e-mail is
intended only for asp_databases@p... It may contain privileged
and confidential information that is exempt from disclosure by law and
if you are not an intended recipient, you must not copy, distribute or
take any action in reliance on it. If you have received this e-mail in
error, you may notify our helpdesk by telephone on 44 (0)161 211 2222
and return the original to the sender. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
contain viruses. The sender (oliver.tomkins@g...) therefore does
not accept liability for any errors or omissions in the contents of this
message, which arise as a result of e-mail transmission. If verification
is required please request a hard-copy version. 

 

 

 


Tracking #: EB9A05BAB16CD6119F4600A0C98331C2C90881CC