[SERVER-4056] make _KeyNode copy operation in btree bucket faster Created: 11/Oct/11 Updated: 10/Dec/14 Resolved: 10/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Guanqun Lu | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | btree, pull-request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
we can utilize 'memmove' instead of copying _KeyNode one by one. |
| Comments |
| Comment by Guanqun Lu [ 11/Oct/11 ] |
|
Pull request https://github.com/mongodb/mongo/pull/112 addresses this issue. To show that memmove does operate faster than copying one by one, there's also a test benchmark included. https://github.com/guanqun/mongo/commit/2115afba96a4cae901f6eef6d257385957245747 |