[SERVER-27452] Performance tune oplog with inMemory storage engine Created: 19/Dec/16 Updated: 06/Dec/22 Resolved: 02/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alexander Gorrod | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
We should craft a test that measures performance over time with the inMemory storage engine where the oplog is configured. It would be interesting to track performance once the oplog becomes full and starts being garbage collected. |
| Comments |
| Comment by Ian Whalen (Inactive) [ 02/Feb/18 ] |
|
Closing as won't fix because we haven't heard any user reports of this being a problem. |