OCIObjectSetAttr performance deteriorates when binding too many Type params

Question

Hi,
In my application, when I passed a Type Array as parameter to the stored procedure and when the Type Array is large enough(normally 3000 type objects， each objects has about 15 attributes), the OCIObjectSetAttr performance deteriorates large enough from below 1 millisecond to 1~3 miliseconds.
I am using OCI 11gR2, does anyone notice it and know how to optimize it?
Regards,
-Bruce

Answer 1

Hi Steve,
Locking algorithms are used to ensure correct behavior when concurrent threads or processes access and update shared data structures. Too many deadlocks is a symptom of too much contention.
One very effective way to reduce contention (and hence deadlocks) is by careful application design. Here are a few things you can do to improve the situation (these are general suggestions; they may or may not be applicable in your application, but certainly worth considering).
- "contention friendly" data model and data - for example, but choosing random (but unique) keys, you will reduce the contention on the b-tree index for concurrent inserts.
- partitioning the data - if you have n threads, and create n databases, where each thread inserts data into its own database, then you'll dramatically reduce the locking contention. If the data files are on separate spindles, you'll also reduce the IO bottleneck.
- keep transactions short
- hold write locks for the shortest possible duration
It may be worth trying some of these ideas.
The next release of Berkeley DB (version 4.8) is coming soon; it has significant enhancements specifically designed to reduce contention. I'd certainly recommend studying the new features and enhancements and then trying out BDB 4.8.
Hope this helps.
Thanks and warm regards.
ashok joshi
Director, Oracle Berkeley DB development