Re: Bad NFS performance for fsync(2)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri 24-05-24 19:08:51, Dan Shelton wrote:
> On Thu, 23 May 2024 at 18:55, Jan Kara <jack@xxxxxxx> 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?

Well, this is somewhat hand-edited fio command that our QA runs as part of
performance testing of our kernels.

								Honza
-- 
Jan Kara <jack@xxxxxxxx>
SUSE Labs, CR




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux