Re: JDBC and Oracle

OK. I haven't looked at any BM test for the different JDBC drivers. You may very well be right that there are faster connectors out there. But my point is that the driver is probably not the bottleneck in the application.
First of all, establishing the connection is the most resource consuming operation. This part you solve by using connection pooling. The sql query istelf in most cases pritty light.
But you should first of all look in to issues as database tuning, correct indexing, chaching of result objects (for instance - a lot of apps have a lot of queries for data that doesnt change much. Like looking up prices etc.). By chaching these you strip the application for a lot of overhead. You may also work with sql tuning if you have complex queries. Check out some of the tools Quest Software have for optimalization of Oracle db's.

"Thomas Kellerer" <no_address_at_gmx.net> skrev i melding news:MPG.17fcd996d74dc0ad989689_at_news...
> aslak_at_poppe.net
> > Oracles JDBC driver is pretty fast.
> > But what you may consider when you have that many querys, is to
 implement a
> > chaching mechanism for objects containg the results. I think Oracle have
> > that, or you could use something like poolman for connection pooling and
> > object chaching.
> > That may speed up things.
> >
>
> I don't think that Oracle's JDBC drivers are pretty fast. I have converted
 a
> database application from PowerBuilder to Java/Swing. While the speed is
 nearly the
> same with MS SQL Server, it is about 2-3 times slower with Oracle's JDBC
 drivers. I
> haven't tested the JDBC driver from INET for Oracle yet (but MS's JDBC
 driver is
> about the same speed as the INET driver)
>
> Thomas
Received on Thu Sep 26 2002 - 11:28:49 CEST