Title: Message
|
The
performance of JDBC OCI vs Thin really depends on what you are trying to
do. Thin driver can perform better
than
OCI and in some situations doesn't. Also there are limitations in Thin
driver such as you can't return
a
PL/SQL table using Thin driver, you can't do TAF etc.
Richard Ji
I've
gone to using the thin driver exclusively, as (counter-intuitively, I know) it
performs better than the OCI driver. Plus it's easier to
port...
My application uses a database
and doesn't seem to scale well. What could be going on?
Oracle provides two types of database drivers: a
type-2 driver, called the OCI (Oracle Call Interface) driver that utilizes
native code, and a type-4 pure Java driver called the thin driver. In single
processor environments, the thin driver works somewhat better than the OCI
driver because of the JNI overhead associated with the OCI driver. On
multi-processor configuations, synchronization points within Solaris used by
the OCI driver become big bottlenecks and prevent scaling. We recommend
using the thin driver in all cases.
Is this actually the case? Does
anyone have more information on this?
Thanks,
Rick
Stephenson
This email and any files transmitted with it are
confidential and intended solely for the use of the individual or entity to
which they are addressed. This message contains confidential information and
is intended only for the individual named. If you are not the named
addressee you should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this e-mail by
mistake and delete this e-mail from your system. If you are not the intended
recipient you are notified that disclosing, copying, forwarding or otherwise
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
|
