From: Wolf Noble <wolf@wolfspyre.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] 10G mesh to 40G DAC
Date: Tue, 22 Feb 2022 10:35:51 -0600 [thread overview]
Message-ID: <FC70217E-EE5D-46F6-A128-8F81CFC343DC@wolfspyre.com> (raw)
In-Reply-To: <639da1da-5e4c-7c13-03cb-ce716cd07954@merit.unu.edu>
Cool!!
is there some set of consistent synthetic action-sets cluster maintainers can perform to illustrate a vaguely useful performance benchmark that would facilitate some objective comparable metrics?
would it be valuable in cases like this?
[= The contents of this message have been written, read, processed, erased, sorted, sniffed, compressed, rewritten, misspelled, overcompensated, lost, found, and most importantly delivered entirely with recycled electrons =]
prev parent reply other threads:[~2022-02-22 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 12:03 mj
2022-02-22 16:35 ` Wolf Noble [this message]
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=FC70217E-EE5D-46F6-A128-8F81CFC343DC@wolfspyre.com \
--to=wolf@wolfspyre.com \
--cc=pve-user@lists.proxmox.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.
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.