[SERVER-18677] Throughput drop during transaction pinned phase of checkpoints under WiredTiger (larger data set) Created: 27/May/15 Updated: 14/Apr/16 Resolved: 16/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.1.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | David Hows |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
In
This was fixed in 3.1.3:
However if the data set is increased to 20M documents a similar problem still appears in 3.1.3. Based on the shapes of the curves it appears this may be a little different issue: in
(Note: C-D is a different issue - see |
| Comments |
| Comment by David Hows [ 16/Jul/15 ] |
|
Marking this as Done based on my testing, as I was unable to reproduce. There have been a number of changes to related parts of MongoDB and WT including the linked |
| Comment by David Hows [ 15/Jul/15 ] |
|
Ran this on an r3.4xlarge using Bruce's setup and MongoDB master as at 15/7/2015 Hash: 3f301ac62e The instance had a generic (slow) SSD storage formatted using XFS. With the 10M workload there was no drop in throughput associated with pinned transaction IDs due to a checkpoint. There was only one small drop in query throughput and this was associated with an increase in writes (update ops). With the 20M workload there was no instance when a trasnaction ID was pinned due to a checkpoint. There were no sustained drops in throughput |
| Comment by Michael Cahill (Inactive) [ 06/Jul/15 ] |
|
david.hows can you please retest against MongoDB master? |