We are using PTS/iperf and having it execute a set of tests. We have observed that, in some cases, not all of the RawString entries are filled. All of the Value entries are there (and are correct as we've checked using debug-run). Here is a snippet of a recent composite.xml file and additional details can be provided, if requested.
There is no RawString entry in the first case (TCP -P 4), yet it is there for the UDP -P 4, TCP -P 16 and UDP -P 16 cases. We can see from the JSON entry that three trials were run for each of these experiments. Note these cases use a slightly modified test-definition.xml, adding these cases to be able to name them individually (versus using the default parallel parameter).
Any thoughts or suggestions? Thanks in advance.
<Result>
<Identifier>pts/iperf-1.0.2</Identifier>
<Title>iPerf</Title>
<AppVersion>3.1.3</AppVersion>
<Arguments>-w 256k -P 4 -t 10 -c 100.100.243.217 -p 5201</Arguments>
<Description>Test: TCP-4 - Duration: 10</Description>
<Scale>Mbits/sec</Scale>
<Proportion>HIB</Proportion>
<DisplayFormat>BAR_GRAPH</DisplayFormat>
<Data>
<Entry>
<Identifier>Red Hat Virtio device</Identifier>
<Value>1042</Value>
<RawString></RawString>
<JSON>{"compiler-options":{"compiler-type":"CC","compiler":"gcc","compiler-options":"-O3 -march=native -lm"},"test-run-times":"10.19:10.18:10.18"}</JSON>
</Entry>
</Data>
</Result>
<Result>
<Identifier>pts/iperf-1.0.2</Identifier>
<Title>iPerf</Title>
<AppVersion>3.1.3</AppVersion>
<Arguments>-u -P 4 -t 10 -c 100.100.243.217 -p 5201</Arguments>
<Description>Test: UDP-4 - Duration: 10</Description>
<Scale>Mbits/sec</Scale>
<Proportion>HIB</Proportion>
<DisplayFormat>BAR_GRAPH</DisplayFormat>
<Data>
<Entry>
<Identifier>Red Hat Virtio device</Identifier>
<Value>4.19</Value>
<RawString>4.19:4.19:4.19</RawString>
<JSON>{"compiler-options":{"compiler-type":"CC","compiler":"gcc","compiler-options":"-O3 -march=native -lm"},"test-run-times":"10.17:10.17:10.17"}</JSON>
</Entry>
</Data>
</Result>
<Result>
<Identifier>pts/iperf-1.0.2</Identifier>
<Title>iPerf</Title>
<AppVersion>3.1.3</AppVersion>
<Arguments>-w 256k -P 16 -t 10 -c 100.100.243.217 -p 5201</Arguments>
<Description>Test: TCP-16 - Duration: 10</Description>
<Scale>Mbits/sec</Scale>
<Proportion>HIB</Proportion>
<DisplayFormat>BAR_GRAPH</DisplayFormat>
<Data>
<Entry>
<Identifier>Red Hat Virtio device</Identifier>
<Value>1043</Value>
<RawString>1044:1043:1043</RawString>
<JSON>{"compiler-options":{"compiler-type":"CC","compiler":"gcc","compiler-options":"-O3 -march=native -lm"},"test-run-times":"10.37:10.22:10.22"}</JSON>
</Entry>
</Data>
</Result>
<Result>
<Identifier>pts/iperf-1.0.2</Identifier>
<Title>iPerf</Title>
<AppVersion>3.1.3</AppVersion>
<Arguments>-u -P 16 -t 10 -c 100.100.243.217 -p 5201</Arguments>
<Description>Test: UDP-16 - Duration: 10</Description>
<Scale>Mbits/sec</Scale>
<Proportion>HIB</Proportion>
<DisplayFormat>BAR_GRAPH</DisplayFormat>
<Data>
<Entry>
<Identifier>Red Hat Virtio device</Identifier>
<Value>16.80</Value>
<RawString>16.8:16.8:16.8</RawString>
<JSON>{"compiler-options":{"compiler-type":"CC","compiler":"gcc","compiler-options":"-O3 -march=native -lm"},"test-run-times":"10.17:10.17:10.17"}</JSON>
</Entry>
</Data>
</Result>
There is no RawString entry in the first case (TCP -P 4), yet it is there for the UDP -P 4, TCP -P 16 and UDP -P 16 cases. We can see from the JSON entry that three trials were run for each of these experiments. Note these cases use a slightly modified test-definition.xml, adding these cases to be able to name them individually (versus using the default parallel parameter).
Any thoughts or suggestions? Thanks in advance.
<Result>
<Identifier>pts/iperf-1.0.2</Identifier>
<Title>iPerf</Title>
<AppVersion>3.1.3</AppVersion>
<Arguments>-w 256k -P 4 -t 10 -c 100.100.243.217 -p 5201</Arguments>
<Description>Test: TCP-4 - Duration: 10</Description>
<Scale>Mbits/sec</Scale>
<Proportion>HIB</Proportion>
<DisplayFormat>BAR_GRAPH</DisplayFormat>
<Data>
<Entry>
<Identifier>Red Hat Virtio device</Identifier>
<Value>1042</Value>
<RawString></RawString>
<JSON>{"compiler-options":{"compiler-type":"CC","compiler":"gcc","compiler-options":"-O3 -march=native -lm"},"test-run-times":"10.19:10.18:10.18"}</JSON>
</Entry>
</Data>
</Result>
<Result>
<Identifier>pts/iperf-1.0.2</Identifier>
<Title>iPerf</Title>
<AppVersion>3.1.3</AppVersion>
<Arguments>-u -P 4 -t 10 -c 100.100.243.217 -p 5201</Arguments>
<Description>Test: UDP-4 - Duration: 10</Description>
<Scale>Mbits/sec</Scale>
<Proportion>HIB</Proportion>
<DisplayFormat>BAR_GRAPH</DisplayFormat>
<Data>
<Entry>
<Identifier>Red Hat Virtio device</Identifier>
<Value>4.19</Value>
<RawString>4.19:4.19:4.19</RawString>
<JSON>{"compiler-options":{"compiler-type":"CC","compiler":"gcc","compiler-options":"-O3 -march=native -lm"},"test-run-times":"10.17:10.17:10.17"}</JSON>
</Entry>
</Data>
</Result>
<Result>
<Identifier>pts/iperf-1.0.2</Identifier>
<Title>iPerf</Title>
<AppVersion>3.1.3</AppVersion>
<Arguments>-w 256k -P 16 -t 10 -c 100.100.243.217 -p 5201</Arguments>
<Description>Test: TCP-16 - Duration: 10</Description>
<Scale>Mbits/sec</Scale>
<Proportion>HIB</Proportion>
<DisplayFormat>BAR_GRAPH</DisplayFormat>
<Data>
<Entry>
<Identifier>Red Hat Virtio device</Identifier>
<Value>1043</Value>
<RawString>1044:1043:1043</RawString>
<JSON>{"compiler-options":{"compiler-type":"CC","compiler":"gcc","compiler-options":"-O3 -march=native -lm"},"test-run-times":"10.37:10.22:10.22"}</JSON>
</Entry>
</Data>
</Result>
<Result>
<Identifier>pts/iperf-1.0.2</Identifier>
<Title>iPerf</Title>
<AppVersion>3.1.3</AppVersion>
<Arguments>-u -P 16 -t 10 -c 100.100.243.217 -p 5201</Arguments>
<Description>Test: UDP-16 - Duration: 10</Description>
<Scale>Mbits/sec</Scale>
<Proportion>HIB</Proportion>
<DisplayFormat>BAR_GRAPH</DisplayFormat>
<Data>
<Entry>
<Identifier>Red Hat Virtio device</Identifier>
<Value>16.80</Value>
<RawString>16.8:16.8:16.8</RawString>
<JSON>{"compiler-options":{"compiler-type":"CC","compiler":"gcc","compiler-options":"-O3 -march=native -lm"},"test-run-times":"10.17:10.17:10.17"}</JSON>
</Entry>
</Data>
</Result>
Comment