adjust perf numbers

Signed-off-by: Serban Iorga <[email protected]>
firecracker-microvm · Jun 3, 2021 · 1b7df37 · 1b7df37
1 parent d20c465
commit 1b7df37
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/tests/integration_tests/build/test_coverage.py b/tests/integration_tests/build/test_coverage.py
@@ -24,7 +24,7 @@
 # this contains the frequency while on AMD it does not.
 # Checkout the cpuid crate. In the future other
 # differences may appear.
-COVERAGE_DICT = {"Intel": 85.15, "AMD": 84.52, "ARM": 83.36}
+COVERAGE_DICT = {"Intel": 85.15, "AMD": 84.52, "ARM": 83.46}
 
 PROC_MODEL = proc.proc_type()
 

diff --git a/tests/integration_tests/performance/test_process_startup_time.py b/tests/integration_tests/performance/test_process_startup_time.py
@@ -10,7 +10,7 @@
 import host_tools.logging as log_tools
 from host_tools.cargo_build import run_seccompiler
 
-MAX_STARTUP_TIME_CPU_US = {'x86_64': 5500, 'aarch64': 3200}
+MAX_STARTUP_TIME_CPU_US = {'x86_64': 5500, 'aarch64': 2800}
 """ The maximum acceptable startup time in CPU us. """
 # TODO: Keep a `current` startup time in S3 and validate we don't regress