[JAVA-610] Make DBCursor finalizer optional and disable it in all cases where there is no cursor maintained on the server Created: 24/Jul/12 Updated: 29/Aug/12 Resolved: 31/Jul/12 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Performance |
| Affects Version/s: | 2.6.5, 2.7.3, 2.8.0 |
| Fix Version/s: | 2.9.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Description |
|
Finalizers can have a negative affect on overall GC throughput. DBApiLayer.Result has a finalize method which pushes the cursor onto a queue of dead cursors for later cleanup. The problem is that driver users still pay the cost of of the finalizer in these cases:
We can address this in two ways
|
| Comments |
| Comment by Jeffrey Yemin [ 29/Aug/12 ] |
|
Closing as part of 2.9.0 release process. |
| Comment by auto [ 02/Aug/12 ] |
|
Author: {u'date': u'2012-08-01T11:52:58-07:00', u'email': u'jeff.yemin@10gen.com', u'name': u'Jeff Yemin'}Message: |
| Comment by auto [ 27/Jul/12 ] |
|
Author: {u'date': u'2012-07-27T08:41:52-07:00', u'email': u'jeff.yemin@10gen.com', u'name': u'Jeff Yemin'}Message: |