----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
> For sure. The system runs as standalone on a PIII500, Apache/JServ runs at
> about 2% - 9%, the JVM at 64Mb. The system is so under-taxed it isnt funny.
> Yet the website/servlet/database serves approx 50 dynamic pages.
:-) I think the significant diff is my use of RMI. All my code that
accessed JDBC
was also using RMI or multicast UDP stuff as well. Whilst my database is
medium size, individual
queries don't yield large data volumes, normally < 25k
> >Concurrency wasn't an issue with my s/w since it
> >crashed the JVM with only one connection to the database.
>
> Have you been using a connection pool to connect to the database rather than
> making a new connection each time from your code? It takes the wear and tear
> out of continually creating new connections plus gives huge "user apparent"
> performance boosts.
Yes. The other advantage of a connection pool is you get better
concurrency since
Connection object access is, AFAIK, normally only concurrent where
threads are in
the same transaction.
> I use an Administrative class which loads on the webserver start up with the
> JServ zone [servlet.startup], the connection pool loads and initializes from
> that class. If the connections crap out they do it at startup that way and
> not when data is being asked for.
I have a 1/2 way house. I create a few initially but grow my pool
dynamically (up to a ceiling)
on demand - that way I don't absorb memory if the number of concurrent
users is low. If a connection
craps out during use the client returns it to the pool and the pool
tries to "re-connect" it. This way
I can handle a databse crashing and restarting. Without this the JDBC
drivers I'm using just complain there
is no database, even after it's restarted - thus must keep some static
link to the database that doesn't
recognise a restart.
BTW: I don't install the product on a dual processor box, I just test it
on one. i've found that
testing supposedly thread safe code on a multi processor box finds more
safety and liveness issues
than doing on on a single processor box where nothing is truly
concurrent.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
