-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
3
-
Storage Engines - 2022-10-17, Storage Engines - 2022-10-31, Storage Engines - 2022-11-14
We have a workload description for the wtperf benchmarking tool that simulates the access pattern of the MongoDB oplog. It can be seen [here|
https://github.com/wiredtiger/wiredtiger/blob/develop/bench/wtperf/runners/mongodb-oplog.wtperf].
We should add that configuration to our automated performance test suite, and start tracking variations in the performance.
This would be a change to the test/evergreen.yml configuration file, similar to:
diff --git a/test/evergreen.yml b/test/evergreen.yml
index 33db05f8d..7a70266e9 100755
--- a/test/evergreen.yml
+++ b/test/evergreen.yml
@@ -3361,6 +3361,21 @@ tasks:
vars:
perf-test-name: modify-force-update-large-record-btree.wtperf
+ - name: perf-test-mongodb-oplog
+ tags: ["btree-perf"]
+ depends_on:
+ - name: compile
+ commands:
+ - func: "fetch artifacts"
+ - func: "run-perf-test"
+ vars:
+ perf-test-name: mongodb-oplog.wtperf
+ maxruns: 3
+ wtarg: -ops ['"load", "insert", "truncate"']
+ - func: "upload-perf-test-stats"
+ vars:
+ perf-test-name: mongodb-oplog.wtperf
+
#########################################
# Performance Tests for perf-checkpoint #
#########################################
- is related to
-
WT-9451 Test to demonstrate append only workloads
-
- Open
-