From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] Some SMP performance measurements.
Date: Fri, 13 Mar 2020 16:52:19 +0000 [thread overview]
Message-ID: <4293af16-2eac-48db-801c-34ae39729e70@www.fastmail.com> (raw)
In-Reply-To: <03e5fb90-cee6-8c3a-3700-e547a2959e1e@qs.co.nz>
Just for comparison, SMP is known to be good for rc-httpd & werc which make heavy use of pipes. I don't know about using many cores for them, but >1 makes a huge difference.
prev parent reply other threads:[~2020-03-13 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 2:38 Trevor Higgins
2020-03-12 12:14 ` [9front] " Steve Simon
2020-03-12 17:14 ` hiro
2020-03-13 16:52 ` Ethan Gardener [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=4293af16-2eac-48db-801c-34ae39729e70@www.fastmail.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.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 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 NNTP newsgroup(s).