« Berkeley DB Java Edition DPL Assistant for Eclipse Available | Main | Berkeley DB Oracle Open World Sessions »

Berkeley DB Java Edition Shared Database Handles

For a long time, we've recommended using separate Database handles in high-concurrency environments. The reason was that there was a hot spot involving maintenance of the list of Cursors used by the Database so that we could flag and close open Cursors at Database.close() time. We finally decided that maintaining this relationship was not worth the overhead and reduction in concurrency. So in JE 4.0 we will remove it. The results will be that sharing Database handles across threads will not incur a performance penalty. But we will also not automatically close Cursors at Database.close() time. The change log entries for this change (when it's available) will refer to [#15413] and [#16346]. Unfortunately, I can't say when this release will be available because of Oracle policies. But I can say that one of the main areas we're emphasizing is performance.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on August 27, 2008 1:02 PM.

The previous post in this blog was Berkeley DB Java Edition DPL Assistant for Eclipse Available.

The next post in this blog is Berkeley DB Oracle Open World Sessions.

Many more can be found on the main index page or by looking through the archives.

Top Tags

Powered by
Movable Type and Oracle