Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Instead of hard coding line speed numbers for rate calcuation,
MoonGen should use its class object initialized at start time.
JIRA: VSPERF-368
Change-Id: I68c688f8c244df16d98cfd15efabf491a317256b
Signed-off-by: bmichalo <bmichalo@redhat.com>
|
|
|
|
For MoonGen, the final results parameters: throughput_rx_percent,
throughput_tx_percent were incorrectly calculated when converting
MoonGen to VSPERF format. In particular, this would occur when more
than one data stream (single channel unidirectional traffic) was used in
the test. When calculating these percentages, only aggregate throughput
values equaling unidirectional traffic were used (for example, for 64
byte frames bidirectional traffic should use 29.76 Mpps, not 14.88 Mpps)
JIRA: VSPERF-341
Change-Id: Ie62bded7aea023c287697f18c4172b58c320e050
Signed-off-by: bmichalo <bmichalo@redhat.com>
|
|
VSPERF framework was updated to follow RFC2544 definition
of 'test' and 'trial' terms. Test parameter 'rfc2544_trials'
was replaced by new parameter 'rfc2544_tests'.
Both code and documentation were updated to reflect
these changes.
JIRA: VSPERF-300
Change-Id: I144a28359fd06394f1f87ef324458bafd5aad45f
Signed-off-by: Martin Klozik <martinx.klozik@intel.com>
Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com>
Reviewed-by: Al Morton <acmorton@att.com>
Reviewed-by: Christian Trautman <ctrautma@redhat.com>
Reviewed-by: <bmichalo@redhat.com>
|
|
The VSPERF traffic profile for starting rate is in a
percentage of line rate. MoonGen programs its
starting rate as Mpps. Therefore the traffic profile
for VSPERF needs to be converted to a MoonGen format.
There was a hardcoding of 14.88 that was used for the
starting frame rate for all frame sizes. This needs
to be corrected to take into account all frame sizes.
JIRA: VSPERF-350
Change-Id: Ied71668a560d7d2b03483f9a1192dd2fb4965996
Signed-off-by: bmichalo <bmichalo@redhat.com>
|
|
Results from other traffic generators are reported as
pure numbers, i.e. 2477356.0000. These values are
consumed and processed by other scripts (e.g. CI or
OPNFV results visualization), so we should keep it
consistent among various traffic generators.
JIRA: VSPERF-342
Change-Id: I305421287eb632707038f2c8bc594fcb255ec939
Signed-off-by: bmichalo <bmichalo@redhat.com>
|
|
MoonGen needs to take into account the VLAN tag 'enable'
control knob defined within the VSPERF traffic profile
and therefore only insert the VLAN tag when its 'True'.
JIRA: VSPERF-329
Change-Id: Idbeed2f7e6411f0c28aa56a2d3e71bd7a79d975a
Signed-off-by: bmichalo <bmichalo@redhat.com>
|
|
Need to change naming to 'Moongen' for consistent naming
between conf files and class
JIRA: VSPERF-323
Change-Id: Ic580b68323a759b3c2ef7ca3c07006243a3acf7d
Signed-off-by: bmichalo <bmichalo@redhat.com>
|
|
Adds support for the MoonGen packet generator.
The following traffic types are included:
* RFC 2544 Throughput: Synchronous Interface
* RFC 2544 Back 2 Back: Synchronous Interface
* Continous Flow: Synchronous Interface
JIRA: VSPERF-168
Sample log of execution can be found as an
attachment within JIRA VSPERF-168
Change-Id: I5bb84290945f4ba41bc962370e643bbbeff0e486
Signed-off-by: bmichalo <bmichalo@redhat.com>
|