[SERVER-17111] Performance minimum at wiredTigerConcurrentWriteTransactions=16 Created: 29/Jan/15 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.0.0-rc7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Backlog - Storage Engines Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Assigned Teams: |
Storage Engines
|
| Operating System: | ALL |
| Participants: |
| Description |
|
For a constant load, as wiredTigerConcurrentWriteTransactions is varied a minimum in performance is seen at a value of 16 concurrent write transactions. Tests below on 6-CPU VMware machine. Insert-only workload, 64 clients:
Mixed (but write-heavy) workload of inserts, updates, queries, 512 clients:
Profile and stats showing effect of changing from (effectively) unlimited to limit of 16 during the middle of a run:
|