From: Dan Shelton <dan.f.shelton@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>
Subject: Re: Bad NFS performance for fsync(2)
Date: Fri, 24 May 2024 19:08:51 +0200 [thread overview]
Message-ID: <CAAvCNcB1hsS67Cy6sZP3Mf33VCKfFsg0Vc0pH2XJt0K6Po9ZQQ@mail.gmail.com> (raw)
In-Reply-To: <20240523165436.g5xgo7aht7dtmvfb@quack3>
On Thu, 23 May 2024 at 18:55, Jan Kara <jack@suse.cz> wrote:
>
> Hello!
>
> I've been debugging NFS performance regression with recent kernels. It
> seems to be at least partially related to the following behavior of NFS
> (which is there for a long time AFAICT). Suppose the following workload:
>
> fio --direct=0 --ioengine=sync --thread --directory=/test --invalidate=1 \
> --group_reporting=1 --runtime=100 --fallocate=posix --ramp_time=10 \
> --name=RandomWrites-async --new_group --rw=randwrite --size=32000m \
> --numjobs=4 --bs=4k --fsync_on_close=1 --end_fsync=1 \
> --filename_format='FioWorkloads.$jobnum'
Where do you get the fio command from?
Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd
next prev parent reply other threads:[~2024-05-24 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 16:54 Bad NFS performance for fsync(2) Jan Kara
2024-05-23 18:00 ` Trond Myklebust
2024-05-24 13:17 ` Jan Kara
2024-05-24 16:16 ` Jan Kara
2024-05-24 17:08 ` Dan Shelton [this message]
2024-05-27 10:32 ` Jan Kara
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=CAAvCNcB1hsS67Cy6sZP3Mf33VCKfFsg0Vc0pH2XJt0K6Po9ZQQ@mail.gmail.com \
--to=dan.f.shelton@gmail.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).