[JAVA-1219] Delay creation of DBDecoder in DBPort until after the socket is successfully opened Created: 13/May/14 Updated: 01/Aug/14 Resolved: 14/May/14 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Performance |
| Affects Version/s: | None |
| Fix Version/s: | 2.12.2 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
In some cases the driver creates DBPort instances at a high rate, and since DBDecoder instances can contain large arrays that put stress on the garbage collector, they should only be constructed after DBPort has successfully connected. |
| Comments |
| Comment by Githook User [ 01/Aug/14 ] |
|
Author: {u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |
| Comment by Githook User [ 14/May/14 ] |
|
Author: {u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |