linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wangyan <wangyan122@huawei.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	<linux-fsdevel@vger.kernel.org>,
	"virtio-fs@redhat.com" <virtio-fs@redhat.com>,
	Miklos Szeredi <mszeredi@redhat.com>
Subject: Re: [Virtio-fs] [QUESTION] A performance problem for buffer write compared with 9p
Date: Thu, 22 Aug 2019 20:48:23 +0800	[thread overview]
Message-ID: <0e8090c7-0c7c-bcbe-af75-33054d3a3efb@huawei.com> (raw)
In-Reply-To: <CAJfpegtBYLJLWM8GJ1h66PMf2J9o38FG6udcd2hmamEEQddf5w@mail.gmail.com>

On 2019/8/22 19:43, Miklos Szeredi wrote:
> On Thu, Aug 22, 2019 at 2:59 AM wangyan <wangyan122@huawei.com> wrote:
>> I will test it when I get the patch, and post the compared result with
>> 9p.
>
> Could you please try the attached patch?  My guess is that it should
> improve the performance, perhaps by a big margin.
>
> Further improvement is possible by eliminating page copies, but that
> is less trivial.
>
> Thanks,
> Miklos
>
Using the same test model. And the test result is:
	1. Latency
		virtiofs: avg-lat is 15.40 usec, bigger than before(6.64 usec).
		4K: (g=0): rw=write, bs=4K-4K/4K-4K/4K-4K, ioengine=psync, iodepth=1
		fio-2.13
		Starting 1 process
		Jobs: 1 (f=1): [W(1)] [100.0% done] [0KB/142.4MB/0KB /s] [0/36.5K/0 
iops] [eta 00m:00s]
		4K: (groupid=0, jobs=1): err= 0: pid=5528: Thu Aug 22 20:39:07 2019
		  write: io=6633.2MB, bw=226404KB/s, iops=56600, runt= 30001msec
			clat (usec): min=2, max=40403, avg=14.77, stdev=33.71
			 lat (usec): min=3, max=40404, avg=15.40, stdev=33.74

	2. Bandwidth
		virtiofs: bandwidth is 280840KB/s, lower than before(691894KB/s).
		1M: (g=0): rw=write, bs=1M-1M/1M-1M/1M-1M, ioengine=psync, iodepth=1
		fio-2.13
		Starting 1 process
		Jobs: 1 (f=1): [f(1)] [100.0% done] [0KB/29755KB/0KB /s] [0/29/0 iops] 
[eta 00m:00s]
		1M: (groupid=0, jobs=1): err= 0: pid=5550: Thu Aug 22 20:41:28 2019
		  write: io=8228.0MB, bw=280840KB/s, iops=274, runt= 30001msec
			clat (usec): min=362, max=11038, avg=3571.33, stdev=1062.72
			 lat (usec): min=411, max=11093, avg=3628.39, stdev=1064.53

According to the result, the patch doesn't work and make it worse than 
before.


  reply	other threads:[~2019-08-22 12:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15  0:30 [QUESTION] A performance problem for buffer write compared with 9p wangyan
2019-08-15  0:56 ` Gao Xiang
2019-08-20  9:16 ` [Virtio-fs] " Stefan Hajnoczi
2019-08-21  7:51   ` Miklos Szeredi
2019-08-21 16:05     ` Stefan Hajnoczi
2019-08-22  0:59       ` wangyan
2019-08-22 11:43         ` Miklos Szeredi
2019-08-22 12:48           ` wangyan [this message]
2019-08-22 13:07             ` Miklos Szeredi
2019-08-22 13:17               ` wangyan
2019-08-22 13:29                 ` Miklos Szeredi
2019-08-22 14:02                   ` Miklos Szeredi
     [not found]                     ` <fd7a2791-d95c-3bd9-e387-b8778a9eca83@huawei.com>
2019-08-26 12:39                       ` Miklos Szeredi
2019-08-28  0:57                         ` wangyan

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=0e8090c7-0c7c-bcbe-af75-33054d3a3efb@huawei.com \
    --to=wangyan122@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-fs@redhat.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 NNTP newsgroup(s).