From f21d9e1a4e6d0a2ed6d7af83191e39a2a883241b Mon Sep 17 00:00:00 2001 From: drebs Date: Fri, 7 Jul 2017 18:17:38 -0300 Subject: [benchmarks] run benchmarks twice, for time and resources We noticed that instrumentation added for watching resources has an impact in time statistics (i.e. it increases average and stddev). This commit makes the benchmark tests run twice: once for measuring time and a second time for measuring resources. --- testing/tests/benchmarks/conftest.py | 8 -------- 1 file changed, 8 deletions(-) (limited to 'testing/tests/benchmarks') diff --git a/testing/tests/benchmarks/conftest.py b/testing/tests/benchmarks/conftest.py index 0d171ef4..ac29f17f 100644 --- a/testing/tests/benchmarks/conftest.py +++ b/testing/tests/benchmarks/conftest.py @@ -22,14 +22,6 @@ server.ensure_server() # pytest customizations # -def pytest_addoption(parser): - parser.addoption( - "--watch-resources", default=False, action="store_true", - help="whether to monitor CPU and memory percentages during test run. " - "**Warning**: enabling this will impact the time taken by the " - "benchmarked code, so use with caution!") - - # mark benchmark tests using their group names (thanks ionelmc! :) def pytest_collection_modifyitems(items): for item in items: -- cgit v1.2.3