From: David Gibson <david@gibson.dropbear.id.au>
To: sbrivio@redhat.com
Cc: passt-dev@passt.top
Subject: Problem with IPv4 performance tests
Date: Tue, 14 Feb 2023 12:59:02 +1100 [thread overview]
Message-ID: <Y+rq5nCQRYxQYkBv@yekko> (raw)
[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]
Hi,
I've been running the tests for the first time since getting back from
holiday. I seem to be getting a consistent failure on the first batch
of IPv4 throughput tests, although the IPv6 tests before it worked fine:
=== perf/passt_tcp
> passt: throughput and latency
Throughput in Gbps, latency in µs, one thread at 4.8 GHz, 8 streams
MTU: | 256B | 576B | 1280B | 1500B | 9000B | 65520B |
|--------|--------|--------|--------|--------|--------|
TCP throughput over IPv6: guest to host | - | - | 6.5 | 7.6 | 20.7 | 28.1 |
TCP RR latency over IPv6: guest to host | - | - | - | - | - | 74 |
TCP CRR latency over IPv6: guest to host | - | - | - | - | - | 227 |
|--------|--------|--------|--------|--------|--------|
TCP throughput over IPv4: guest to host | 0 | 0 | 0 | 0 | 0 | 0 |
TCP RR latency over IPv4: guest to host | - | - | - | - | - |
I haven't seen a failure like this before, has anyone else seen
something like this?
I'm not getting any messages from the iperf client at all - like it
has no connectivity whatsoever, but the non-perf tests are all
passing.
Haven't done much troubleshooting yet.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-02-14 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 1:59 David Gibson [this message]
2023-02-14 14:22 ` Problem with IPv4 performance tests Stefano Brivio
2023-02-15 5:50 ` David Gibson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+rq5nCQRYxQYkBv@yekko \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).