[SERVER-20623] 10% Performance Regression in update path between 3.1.2 and master (Update.IncFewDocs, Update.IncNoIndex, Update.IncWithIndex, MultiUpdate.Uncontended.TwoDocs.NoIndex...) Created: 11/Sep/15 Updated: 06/Dec/22 Resolved: 17/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance, Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Daly | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | mpreg | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
Mongo-perf shows a large regression on all of the update tests sometime between 3.1.2 and 3.1.4 on wiredTiger, probably over multiple commits, and another ~4% drop since 3.1.4. On WiredTiger and MMAPv1, although the regression shows earlier on wiredTiger. WiredTiger Results Two simplified shell based reproductions. Update.MultiUpdate.Uncontended.TwoDocs.NoIndex
Update.FieldAtOffset
|
| Comments |
| Comment by Eric Milkie [ 17/Nov/16 ] |
|
While it would be desirable to understand what exactly caused this particular slowdown, I don't think it's a reasonable use of resources to spend on it. |
| Comment by Githook User [ 11/Dec/15 ] |
|
Author: {u'username': u'dalyd', u'name': u'dalyd', u'email': u'david.daly@mongodb.com'}Message: Overrides for |
| Comment by David Daly [ 30/Nov/15 ] |
|
With recent commits between rc3 and rc4, this regression is less than 5% in general for standalone However the WT with replication still shows a drop from 3.1.2, that occurred between 3.1.2 and 3.1.4. Results here |
| Comment by David Daly [ 24/Nov/15 ] |
|
Also MultiUpdate.Uncontended.TwoDocs.NoIndex shows on 1Node MMAP in similar pattern. |
| Comment by Githook User [ 26/Oct/15 ] |
|
Author: {u'username': u'ksuarz', u'name': u'Kyle Suarez', u'email': u'ksuarz@gmail.com'}Message: This overrides the performance regression in the update tests for WT standalone Signed-off-by: David Daly <david.daly@mongodb.com> |
| Comment by Chung-yen Chang [ 14/Oct/15 ] |
|
Just checked the latest data against 3.1.2 and we are still regressed. The worst regressions are for doc validation updates. For both storage engines, we saw close to 20% of regressions for the updates with doc validation. The other cases are seeing roughly 10% for wiredTiger and ~5% for mmapv1. |
| Comment by Chung-yen Chang [ 17/Sep/15 ] |
|
This is a regression that happened quite a while back. Moving it into the CAP project for proper investigation. |