From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] 9p server to multiply 9p messages?
Date: Tue, 31 May 2022 20:27:52 +0200 [thread overview]
Message-ID: <CAFSF3XPN46dqnKKomAEu7kgqntTUN2ErNdu=L70zwUe5GS=buA@mail.gmail.com> (raw)
In-Reply-To: <CAP6exYJFJJ8EpLKXy4ZNEmtjLiQXxPPEg8NuRODUz=Gep30FVw@mail.gmail.com>
so virtiofs is not using 9p any more?
and with 10 million parallel requests, why shouldn't 9p be able to
deliver 10GB/s ?!
On 5/31/22, ron minnich <rminnich@gmail.com> wrote:
> On Mon, May 30, 2022 at 12:21 AM Bakul Shah <bakul@iitbombay.org> wrote:
>> 9p itself is low performance but that is a separate issue.
>
> Bakul, what are the units? It might be helpful to quantify this
> statement. Are you possibly conflating Plan 9 file systems being slow
> and 9p being slow?
>
> As Rob pointed out in 2013, "If go install is slow on Plan 9, it's
> because Plan 9's file system is
> slow (which it is and always has been)", so slowness in Plan 9 file
> systems is to be expected.
>
> 9p itself does have its limits, which is why Bell Labs Antwerp started
> an effort in 2011 to replace it, but the new work never went very far.
>
> I also know of a number of efforts in the virtualization world where
> 9p was discarded for performance reasons. It's hard to argue with the
> 100x performance improvement that comes with virtiofs, for example.
>
> Gvisor is replacing 9p: https://github.com/google/gvisor/milestone/6.
> Although, in the latter case, I would argue the problem is more with
> Linux limitations than 9p limitations -- linux can't seem to walk more
> than one pathname component at a time, for example, since it has the
> old school namei loop.
>
> But I'm wondering if you have a measurement with numbers.
>
> For rough order of magnitude, HPC file systems can deliver 10 Gbytes/
> second for file reads nowadays, but getting there took 20 years of
> work. When we ran Plan 9 on Blue Gene, with the 6 Gbyte/second
> toroidal mesh connect for each node, we never came remotely close to
> that figure.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T769854fafd2b7d35-M650fba778076835adf9ce8df
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-05-31 18:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 16:02 fgergo
2022-05-28 18:43 ` Skip Tavakkolian
2022-05-28 19:21 ` ron minnich
2022-05-29 10:33 ` fgergo
2022-05-29 10:23 ` fgergo
2022-05-29 11:41 ` fgergo
2022-05-29 23:16 ` Bakul Shah
2022-05-30 4:59 ` ori
2022-05-30 7:19 ` Bakul Shah
2022-05-30 8:03 ` fgergo
2022-05-30 8:35 ` hiro
2022-05-31 16:14 ` ron minnich
2022-05-31 18:27 ` hiro [this message]
2022-05-31 18:35 ` ori
2022-06-01 12:00 ` ron minnich
2022-06-01 14:51 ` ori
2022-06-01 15:31 ` hiro
2022-06-01 15:39 ` hiro
2022-06-01 16:01 ` ori
2022-06-01 4:26 ` Bakul Shah
2022-06-01 7:25 ` hiro
2022-06-01 15:55 ` Jacob Moody
2022-06-01 17:56 ` Steve Simon
2022-06-01 22:29 ` hiro
2022-05-30 8:33 ` hiro
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='CAFSF3XPN46dqnKKomAEu7kgqntTUN2ErNdu=L70zwUe5GS=buA@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9fans@9fans.net \
/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).