From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: George Dunlap <george.dunlap@cloud.com>
Cc: Demi Marie Obenour <demi@invisiblethingslab.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
Juergen Gross <jgross@suse.com>
Subject: Re: Sketch of an idea for handling the "mixed workload" problem
Date: Mon, 22 Jan 2024 13:17:41 +0100 [thread overview]
Message-ID: <Za5c5pm9Qai82zvf@mail-itl> (raw)
In-Reply-To: <CA+zSX=YNjVaGn8=kio=2iT8onHAP61pzP-dicMrr4pKJQ827gw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On Mon, Jan 22, 2024 at 11:54:14AM +0000, George Dunlap wrote:
> The other issue I have with this (and essentially where I got stuck
> developing credit2 in the first place) is testing: how do you ensure
> that it has the properties that you expect?
Audio is actually quite nice use case at this, since it's quite
sensitive for scheduling jitter. I think even a simple "PCI passthrough a
sound card and play/record something" should show results. Especially
you can measure how hard you can push the system (for example artificial
load in other domains) until it breaks.
> How do you develop a
> "regression test" to make sure that server-based workloads don't have
> issues in this sort of case?
For this I believe there are several benchmarking methods already,
starting with old trusty "Linux kernel build time".
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-01-22 12:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 16:42 Sketch of an idea for handling the "mixed workload" problem George Dunlap
2023-09-30 23:28 ` Demi Marie Obenour
2023-10-02 11:20 ` George Dunlap
2024-01-21 23:46 ` Demi Marie Obenour
2024-01-22 0:31 ` Demi Marie Obenour
2024-01-22 11:54 ` George Dunlap
2024-01-22 12:17 ` Marek Marczykowski-Górecki [this message]
2024-01-22 12:25 ` George Dunlap
2024-01-22 12:50 ` Marek Marczykowski-Górecki
2024-01-22 13:02 ` George Dunlap
2024-01-22 13:03 ` George Dunlap
2024-01-23 16:58 ` Demi Marie Obenour
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=Za5c5pm9Qai82zvf@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=demi@invisiblethingslab.com \
--cc=george.dunlap@cloud.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xenproject.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.