RE: Oracle OCI JDBC Driver Not Recommended for Multiprocessor Mac
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 -Original Message-From: Jeremy Pulcifer [mailto:[EMAIL PROTECTED]Sent: Wednesday, April 02, 2003 12:14 PMTo: Multiple recipients of list ORACLE-LSubject: RE: Oracle OCI JDBC Driver Not Recommended for Multiprocessor Mac 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... -Original Message-From: Rick Stephenson [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 7:29 AMTo: Multiple recipients of list ORACLE-LSubject: Oracle OCI JDBC Driver Not Recommended for Multiprocessor Machine Sun's FAQ on java hotspot VM performance (http://java.sun.com/docs/hotspot/PerformanceFAQ.html)includes this interesting question: 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.
RE: Oracle OCI JDBC Driver Not Recommended for Multiprocessor Mac
Rick - In Java Programming for Oracle by Don Bales, he ran some comparative tests showing the comparative advantages of each interface under different circumstances. http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?userid=6WIANMIL0 H http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?userid=6WIANMIL 0Hisbn=059600088Xitm=2 isbn=059600088Xitm=2 Dennis Williams DBA, 40%OCP, 100% DBA Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Thursday, April 03, 2003 10:44 AM To: Multiple recipients of list ORACLE-L 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 -Original Message- Sent: Wednesday, April 02, 2003 12:14 PM To: Multiple recipients of list ORACLE-L 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... -Original Message- Sent: Wednesday, April 02, 2003 7:29 AM To: Multiple recipients of list ORACLE-L Sun's FAQ on java hotspot VM performance ( http://java.sun.com/docs/hotspot/PerformanceFAQ.html) http://java.sun.com/docs/hotspot/PerformanceFAQ.html) includes this interesting question: BM_24My 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. http://java.sun.com/docs/hotspot/PerformanceFAQ.html 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. -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: DENNIS WILLIAMS INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: Oracle OCI JDBC Driver Not Recommended for Multiprocessor Mac
Title: Message 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... -Original Message-From: Rick Stephenson [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 7:29 AMTo: Multiple recipients of list ORACLE-LSubject: Oracle OCI JDBC Driver Not Recommended for Multiprocessor Machine Sun's FAQ on java hotspot VM performance (http://java.sun.com/docs/hotspot/PerformanceFAQ.html)includes this interesting question: 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.
