From 12c3608c3464add7664e3b8f41b07b9b8fd03f1c Mon Sep 17 00:00:00 2001 From: Tibor Frank Date: Thu, 9 Jul 2020 11:16:19 +0200 Subject: Report 2005: Add data, review graphs Change-Id: I2913ed579369a26a1226cfbe958432d1b3e11789 Signed-off-by: Tibor Frank --- .../test_environment_pre_test_server_calib.rst | 26 ++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 docs/report/introduction/test_environment_pre_test_server_calib.rst (limited to 'docs/report/introduction/test_environment_pre_test_server_calib.rst') diff --git a/docs/report/introduction/test_environment_pre_test_server_calib.rst b/docs/report/introduction/test_environment_pre_test_server_calib.rst new file mode 100644 index 0000000000..325c61b212 --- /dev/null +++ b/docs/report/introduction/test_environment_pre_test_server_calib.rst @@ -0,0 +1,26 @@ +Pre-Test Server Calibration +--------------------------- + +Number of SUT server sub-system runtime parameters have been identified +as impacting data plane performance tests. Calibrating those parameters +is part of FD.io CSIT pre-test activities, and includes measuring and +reporting following: + +#. System level core jitter - measure duration of core interrupts by + Linux in clock cycles and how often interrupts happen. Using + `CPU core jitter tool `_. + +#. Memory bandwidth - measure bandwidth with `Intel MLC tool + `_. + +#. Memory latency - measure memory latency with Intel MLC tool. + +#. Cache latency at all levels (L1, L2, and Last Level Cache) - measure + cache latency with Intel MLC tool. + +Measured values of listed parameters are especially important for +repeatable zero packet loss throughput measurements across multiple +system instances. Generally they come useful as a background data for +comparing data plane performance results across disparate servers. + +Following sections include measured calibration data for testbeds. -- cgit 1.2.3-korg