[SERVER-20195] Performance regression in WiredTiger in 3.1.8 Created: 29/Aug/15  Updated: 29/Aug/15  Resolved: 29/Aug/15

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Michael Cahill (Inactive) Assignee: Michael Cahill (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-20193 Performance regression in Single-thre... Closed
Related
is related to SERVER-19445 Performance regression in Mongo-Perf ... Closed
is related to WT-2066 Update the oldest transaction ID from... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

https://evergreen.mongodb.com/task/performance_linux_wt_repl_singleThreaded_a7338c436160e259d0b20058f0a9ae4b442ca102_15_08_28_06_06_32

This is the same issue as SERVER-19445 – if the oldest transaction ID tracked by WiredTiger falls behind, workloads that do many updates to medium-large documents to hit forced eviction. The regression was introduced by WT-2066.


Generated at Thu Feb 08 03:53:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.