Files
mongo/etc/performance_thresholds.yml
adriangzz 4d90658f44 SERVER-102372 Update sep benchmark for auditClientAttrs permission check (#33544)
GitOrigin-RevId: e95263eb1ae8d9d755e67452a24d2cabf2972200
2025-04-10 01:00:39 +00:00

85 lines
3.7 KiB
YAML

########################################################################################################
# This file contains thresholds for performance tests run by resmoke. These correspond to #
# the GenerateAndCheckPerfResults hook. Thresholds are set on a per variant basis. #
# Make sure to set the --variantName flag when running benchmarks in resmoke. #
# #
# Each entry should follow the format below #
########################################################################################################
#
# tests:
# test1:
# variant1:
# - thread_level: {thread_level_value}
# metrics:
# - name: {name of the metric to check}
# value: {Whatever the threshold to check against is}
# bound_direction: {What the threshold direction should be. Must be one of upper or lower}
# - thread_level: {thread_level_value}
# metrics:
# - name: {name of the metric to check}
# value: {Whatever the threshold to check against is}
# bound_direction: {What the threshold direction should be. Must be one of upper or lower}
# test2:
# variant1:
# - thread_level: {thread_level_value}
# metrics:
# - name: {name of the metric to check}
# value: {Whatever the threshold to check against is}
# bound_direction: {What the threshold direction should be. Must be one of upper or lower}
# - thread_level: {thread_level_value}
# metrics:
# - name: {name of the metric to check}
# value: {Whatever the threshold to check against is}
# bound_direction: {What the threshold direction should be. Must be one of upper or lower}
#
#
#
#
# Bound direction upper means that the value reported by the test must be BELOW the threshold value.
# Bound direction lower means that the value reported by the test must be ABOVE the threshold value.
#
#
########################################################################################################
tests:
# The current suggested method for raising these values is to run the
# benchmark a few times in patches, and comparing to the recent history.
# From the benchmark's history page, obtain a "stable region mean"
# and "CV of stable region". These are available in the "Trend Charts" tab on
# Evergreen for the `benchmarks_sep` task.
#
# The deviations of these metrics are extremely tight.
# We can easily accept 2 standard deviations up from the stable mean.
#
# threshold = mean * (1 + 2 * (100 * cv))
#
# 2025-02-16:
# Router/1: mean=20077, cv=.0228 => threshold=20993
# Router/32: mean=20111, cv=.0227 => threshold=21024
# Shard/1: mean=21619, cv=.0008 => threshold=25078
# Shard/32: mean=21695, cv=.0006 => threshold=24298
ServiceEntryPointRouterRoleBenchmarkFixture/BM_SEP_PING:
al2023-arm64-sep-benchmark:
- thread_level: 1
metrics:
- name: instructions_per_iteration_mean
value: 20993
bound_direction: upper
- thread_level: 32
metrics:
- name: instructions_per_iteration_mean
value: 21024
bound_direction: upper
ServiceEntryPointShardRoleBenchmarkFixture/BM_SEP_PING:
al2023-arm64-sep-benchmark:
- thread_level: 1
metrics:
- name: instructions_per_iteration_mean
value: 25078
bound_direction: upper
- thread_level: 32
metrics:
- name: instructions_per_iteration_mean
value: 24298
bound_direction: upper