public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2] RFC: Benchmarking script
Date: Fri, 5 Apr 2024 20:10:26 +0200	[thread overview]
Message-ID: <20240405201026.54877fa2@elisabeth> (raw)
In-Reply-To: <20240405061222.15966-1-david@gibson.dropbear.id.au>

On Fri,  5 Apr 2024 17:12:21 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:

> Although we make some performance measurements in our regular testsuite,
> those are designed more for getting a quick(ish) rough idea of the
> performance, rather than a more precise measurement.
> 
> This patch adds a Python script in contrib/benchmark which can make more
> detailed benchmarks.  It can test both passt & pasta themselves, but also
> various other scenarios for comparison, such as kernel veth, qemu -net tap
> and slirp (either qemu -net user or slirp4netns).

Hah, nice. I haven't tried or reviewed this yet, but I just realised
one thing: iperf3 3.16 finally implements separate streams (-P) as
multiple threads! See:

  https://github.com/esnet/iperf/pull/1591

or release notes. That also means that the whole parallel process
nonsense in the regular suite can finally go away, I guess. I haven't
tested that yet, though.

By the way of that, you mentioned in the past that you had some
throughput failures with UDP tests. Well, I looked into 3.16 changes
because of that -- they started failing for me as well with the new
version. I temporarily reverted back to 3.14 on my system, until we
figure out how to adjust to the new meaning of the "-P" option.

Another thing that occurred to me: it would probably be helpful to
already have vhost-user cases for passt here.

Anyway, I'll give this a try soon. I can also apply it right away if
you prefer.

-- 
Stefano


  reply	other threads:[~2024-04-05 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05  6:12 [PATCH v2] RFC: Benchmarking script David Gibson
2024-04-05 18:10 ` Stefano Brivio [this message]
2024-04-06  3:31   ` 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=20240405201026.54877fa2@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    /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).