Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
-
5
-
Storage - Ra 2021-10-18
-
v5.1
Description
Jenkins perf jobs are unstable at the moment as there are "WARNINGS" in the log output.
For example, the warnings from wiredtiger-perf-btree are:
Tracking stability of READ_COUNT 25210963
|
+ ../../../bench/wtperf/runners/wtperf_track.sh -c medium_read_count 25210963
|
wiredtiger-perf-btree: build #9659: curval=25210963 v3=25546116 v20=25677288.500 v100=29149025.640 pct=5
|
wiredtiger-perf-btree: build #9659: long term trend: WARNING: count 25677288.500 not within 5% of 29149025.640 (curval=25210963)
|
|
|
.......
|
|
|
Tracking stability of READ_COUNT 25641875
|
+ ../../../bench/wtperf/runners/wtperf_track.sh -c medium_read_count 25641875
|
wiredtiger-perf-btree: build #9659: curval=25641875 v3=25641875 v20=25661990.300 v100=29136172.460 pct=5
|
wiredtiger-perf-btree: build #9659: long term trend: WARNING: count 25661990.300 not within 5% of 29136172.460 (curval=25641875)
|
The warnings indicate that our performance has regressed by more than the default threshold of 5%. The scope of this ticket is understand what change on develop branch has introduced this regression.