[SERVER-16868] Significant slowdown in capped collection performance when cap reached Created: 15/Jan/15 Updated: 24/Jan/15 Resolved: 22/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.8.0-rc5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Darren Wood | Assignee: | Mathias Stearn |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Steps To Reproduce: | Same workload and setup as
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
When a smaller cache is used (1GB) and a high insert workload is applied to a capped collection, high insert latencies are seen once the collection reaches the capped value. |
| Comments |
| Comment by Githook User [ 16/Jan/15 ] |
|
Author: {u'username': u'michaelcahill', u'name': u'Michael Cahill', u'email': u'michael.cahill@wiredtiger.com'}Message: |