Well, you can improve your database access times, by opening a permament
database connection. You can place that code, in the servlet's init method. This
connection will stay "open" until the servlet's destroy method is
called. So, you need to add code in your destroy method, that will
disconnect your servlet from your DBMS.
Also, if your DBMS, supports "stored procedures", then you can use them,
since this will speed-up your interaction with the database. If you'r DBMS does
not support them, then you can use "Prepared Statements", which are faster than
the normal Statement (in some cases, at least).
Hope I'v helped,
Regards
Slavikos
##########################################################################
Filippos Slavik
Part of the SIAMS's implementation development team. For more
information, please check http://www.siams.net
e-mail : [EMAIL PROTECTED]
##########################################################################
Filippos Slavik
Part of the SIAMS's implementation development team. For more
information, please check http://www.siams.net
e-mail : [EMAIL PROTECTED]
##########################################################################
----- Original Message -----From: Oguz BaktirSent: Sunday, May 02, 1999 4:18 PMSubject: ConnectionPooling Help NEEDED.
Date: 05/01/99 13:32
From: [EMAIL PROTECTED]@lnisgatt
Subject: global ConnectionPooling
NRRQ
Hi!
Can anyone help me about Connection Pooling?
What is local ConnectionPooling and what is global ConnectionPooling?
What is the advantage of one to the other?
My ListMemberDataServlet takes 6 rows -16 columns each- in 30000msec on the
avarage. How can I improve this? Is there something wrong?
I'm using a P133 with 80mb RAM, and Win98 with MsAccess 97.
Thanks for all.
Regards,
Oguz
