######################################################################################################## # 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: ServiceEntryPointRouterRoleBenchmarkFixture/BM_SEP_PING: al2023-arm64-sep-benchmark: # The current suggested method for raising these values is to run the benchmark a few times in patches, get the # means of these metrics in them, and then multiply them by 1.002 (+ .2%). Please make sure the new values # are above the maximum values reported in those patches to prevent any future flakiness. - thread_level: 1 metrics: - name: instructions_per_iteration_mean value: 20616 bound_direction: upper - thread_level: 32 metrics: - name: instructions_per_iteration_mean value: 20642 bound_direction: upper ServiceEntryPointShardRoleBenchmarkFixture/BM_SEP_PING: al2023-arm64-sep-benchmark: # The current suggested method for raising these values is to run the benchmark a few times in patches, get the # means of these metrics in them, and then multiply them by 1.002 (+ .2%). Please make sure the new values # are above the maximum values reported in those patches to prevent any future flakiness. - thread_level: 1 metrics: - name: instructions_per_iteration_mean value: 23154 bound_direction: upper - thread_level: 32 metrics: - name: instructions_per_iteration_mean value: 23184 bound_direction: upper