How are you managing connections? Are you:
1. managing a connection pool
2. using per session connections with a short timeout
3. using one connection and synchronizing on it
4. using the single thread model to assure no shared data
-----Original Message-----
From: partha [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 17, 1999 1:18 PM
To: [EMAIL PROTECTED]
Subject: Servlet performance in Java Web Server 1.1.3
in Win NT
Hi,
I was on the performance testing of servlet using Java Web
Server 1.1.3
on NT. I cd. found it's pretty slow.
My Servlet was just reading an value from database(Access),
incrementing and
putting
back the result with every access/hit.
My Observation was, The servlet works pretty fine for 100
hits. After That
it's performance
decreses drastically.
Any Comments/Sugession?
Regards
Partha
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body
of the message "signoff SERVLET-INTEREST".
Archives:
http://archives.java.sun.com/archives/servlet-interest.html
Resources:
http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
