Re: Network performance with small packets - continued

[Tom Lendacky <tahm@linux.vnet.ibm.com>]

On Wednesday, March 09, 2011 01:17:44 am Michael S. Tsirkin wrote:
> On Mon, Mar 07, 2011 at 04:31:41PM -0600, Tom Lendacky wrote:
> > I used the uperf tool to do this after verifying the results against
> > netperf. Uperf allows the specification of the number of connections as
> > a parameter in an XML file as opposed to launching, in this case, 100
> > separate instances of netperf.
> 
> Could you post the XML on the list please?

Environment variables are used to specify some of the values:
  uperf_instances=100
  uperf_dest=192.168.100.28
  uperf_duration=300
  uperf_tx_msgsize=256
  uperf_rx_msgsize=256

You can also change from threads to processes by specifying nprocs instead of 
nthreads in the group element.  I found this out later so all of my runs are 
using threads. Using processes will give you some improved peformance but I 
need to be consistent with my runs and stay with threads for now.

<?xml version="1.0"?>
<profile name="TCP_RR">
  <group nthreads="$uperf_instances">
        <transaction iterations="1">
            <flowop type="connect" options="remotehost=$uperf_dest 
protocol=tcp"/>
        </transaction>
        <transaction duration="$uperf_duration">
            <flowop type="write" options="size=$uperf_tx_msgsize"/>
            <flowop type="read"  options="size=$uperf_rx_msgsize"/>
        </transaction>
        <transaction iterations="1">
            <flowop type="disconnect" />
        </transaction>
  </group>
</profile>