Hi Sai, In UDP testing PPS represents packets sent by iperf client to server. Loss is the percentage of packets that were not received by server (more specifically the server tracks packets and sums gaps between of them, https://github.com/esnet/iperf/blob/3.0.7/src/iperf_udp.c#L64). While reported PPS depends on bandwidth and concurrency it makes sense to increase them until loss starts going up, meaning that the communication channel is near the limit. Thanks, Ilya 2017-01-21 1:19 GMT+04:00 Sai Sindhur Malleni <smalleni at redhat.com>: > Hey, > > When using the "iperf3" class in shaker for looking at UDP small packet > performance, we see that as we scale up the concurrency the average PPS > goes up and also the loss % increases. Is the loss % a percentage of the > PPS or does the PPS only represent successful transmissions? Thanks! > > -- > Sai Sindhur Malleni > Software Engineer > Red Hat Inc. > 100 East Davie Street > Raleigh, NC, USA > Work: (919) 754-4557 | Cell: (919) 985-1055 > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170123/d8ad552c/attachment.html>