[SERVER-22407] 7% performance regression in count for mongo-perf Commands.CountsIntIDRange Created: 01/Feb/16 Updated: 16/Mar/16 Resolved: 22/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.3.2 |
| Fix Version/s: | 3.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Daly | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | mpreg | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Query 10 (02/22/16), Query 11 (03/14/16) | ||||||||
| Participants: | |||||||||
| Description |
|
Mongo-perf regression tests show an approximately 7% performance regression in the Commands.CounsIntIDRange test around commit dac2f722f8 commit from |
| Comments |
| Comment by Githook User [ 22/Feb/16 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: Fixes most of a 7% perf regression for COUNT_SCAN plans. |