diff options
| author |   fmenguy <francoisregis.menguy@orange.com> | 2020-09-22 17:10:10 +0200 |
|---|---|---|
| committer | fmenguy <francoisregis.menguy@orange.com> | 2020-10-05 11:34:07 +0200 |
| commit | 94845d2bf7416d8b59e2eaf017244832cf3277f4 (patch) | |
| tree | 945df71df19229ee5aa4ab227811bedece9442ff /docs/testing/user/userguide | |
| parent | 64579b717d47ab7f654c574794831be984bf32e1 (diff) | |
NFVBENCH-177: Add a config item 'user_info' and theoretical max rate value
Change-Id: If96ccbffab67cfc0a08279d94cf7a5e81d958044
Signed-off-by: fmenguy <francoisregis.menguy@orange.com>
Diffstat (limited to 'docs/testing/user/userguide')
| -rw-r--r-- | docs/testing/user/userguide/advanced.rst | 48 |
1 files changed, 47 insertions, 1 deletions
diff --git a/docs/testing/user/userguide/advanced.rst b/docs/testing/user/userguide/advanced.rst index ba212c5..62d17b6 100644 --- a/docs/testing/user/userguide/advanced.rst +++ b/docs/testing/user/userguide/advanced.rst @@ -500,4 +500,50 @@ Check on the NFVBench window that the following log appears just before the test 2019-10-21 09:38:51,532 INFO Running traffic generator 2019-10-21 09:38:51,541 INFO ``Service mode is enabled`` 2019-10-21 09:38:52,552 INFO TX: 2004; RX: 2003; Est. Dropped: 1; Est. Drop rate: 0.0499% - 2019-10-21 09:38:53,559 INFO TX: 4013; RX: 4011; Est. Dropped: 2; Est. Drop rate: 0.0498%
\ No newline at end of file + 2019-10-21 09:38:53,559 INFO TX: 4013; RX: 4011; Est. Dropped: 2; Est. Drop rate: 0.0498% + +User info data +-------------- + +The ``--user-info`` option allows you to pass custom information as a JSON string. +This information will be available through JSON output and also exported to ``fluentd`` and can be used in results post-processing. + +Example of use : + +.. code-block:: bash + + nfvbench ``--user-info='{"status":"explore","description":{"target":"lab","ok":true,"version":2020}'`` + +.. note:: only JSON string is allowed + +``--user-info`` can be used for determining theoretical max rate. In some cases, an overhead encapsulation exists between NFVbench and SUT so NFVbench will not reach line rate inside SUT due to this extra encapsulation. +To calculate this theoretical line rate inside SUT, NFVbench will use a reserved key: ``extra_encapsulation_bytes`` in ``--user-info`` property. + +.. code-block:: bash + + nfvbench ``--user-info='{"extra_encapsulation_bytes": 28}'`` + + +As a result, NFVbench will return two values ``theoretical_tx_rate_bps`` and ``theoretical_tx_rate_pps``: + +.. code-block:: bash + + "ndr": { + "duration_sec": 2.0, + "initial_rate_type": "rate_percent", + "l2frame_size": "64", + "load_percent_per_direction": 100.0, + "rate_bps": 20000000000.0, + "rate_percent": 200.0, + "rate_pps": 29761904, + "stats": { + ... + "offered_tx_rate_bps": 15000000000.0, + ... + "theoretical_tx_rate_bps": 15000000000.0, + "theoretical_tx_rate_pps": 22321428.57142857, + "total_tx_rate": 22321428 + }, + +In the above example, line rate is 20Gbps but NFVbench is outside SUT and a SDN gateway add an extra encapsulation of 28 bytes. +Overall, theoretical line rate inside SUT is only 15 Gbps for 64 bytes packet size and it will be this max capacity treated by the target compute node. |