9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] 9p server to multiply 9p messages?
Date: Wed, 1 Jun 2022 18:56:50 +0100	[thread overview]
Message-ID: <5F09745B-3A68-4E27-B5B5-644605A485ED@quintile.net> (raw)
In-Reply-To: <83022bf9-96d9-d33c-d670-7b90961d61d6@posixcafe.org>

for performance testing why not copy from ramfs on one machine to ramfs on another?

the suggestion from a 9con passim was to have fossil/cwfs/hjfs etc add a Qid type flag to files indicating they are from backing store (QTSTABLE ?)and thus may be copied in parallel. devices and synthetic would not normally have this flag forcing the read or write be sequential.

you could even make the file server set this flag only on files that have not changed in X days, and thus the contents are more likely to be stable (idea from the SRC package from DEC)

perhaps i missed something but i always thought the idea had legs.

-Steve


> On 1 Jun 2022, at 4:56 pm, Jacob Moody <moody@posixcafe.org> wrote:
> 
> hjfs is not exactly known for it's speed[0]. Running a cwfs
> without a worm[1] is likely a more interesting comparison.
> 
> I also would recommend using kvik's clone[2] for copying
> in parallel.
> 
> Would be curious how that stacks up.
> 
> Thanks,
> moody
> 
> [0] http://fqa.9front.org/fqa4.html#4.3.6
> [1] http://fqa.9front.org/fqa4.html#4.3.6.1
> [2] https://git.sr.ht/~kvik/clone

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T769854fafd2b7d35-M45fdc663ef275e87c9b77f37
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-06-01 17:57 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
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 [this message]
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=5F09745B-3A68-4E27-B5B5-644605A485ED@quintile.net \
    --to=steve@quintile.net \
    --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).