linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Ashish Samant <ashish.samant@oracle.com>
Cc: Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	fuse-devel <fuse-devel@lists.sourceforge.net>,
	Srinivas Eeda <srinivas.eeda@oracle.com>
Subject: Re: fuse scalability part 1
Date: Fri, 25 Sep 2015 14:11:31 +0200	[thread overview]
Message-ID: <CAJfpegsgjV2ePkdjZDAi5GoJ5M-Zeoy10v-5p+bzyHVAnGQpuA@mail.gmail.com> (raw)
In-Reply-To: <56044C66.1090207@oracle.com>

On Thu, Sep 24, 2015 at 9:17 PM, Ashish Samant <ashish.samant@oracle.com> wrote:

> We did some performance testing without these patches and with these patches
> (with -o clone_fd  option specified). We did 2 types of tests:
>
> 1. Throughput test : We did some parallel dd tests to read/write to FUSE
> based database fs on a system with 8 numa nodes and 288 cpus. The
> performance here is almost equal to the the per-numa patches we submitted a
> while back.Please find results attached.

Interesting.  This means, that serving the request on a different NUMA
node as the one where the request originated doesn't appear to make
the performance much worse.

Thanks,
Miklos

  reply	other threads:[~2015-09-25 12:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 15:13 fuse scalability part 1 Miklos Szeredi
2015-09-24  1:13 ` Ashish Samant
     [not found] ` <20150814101453.GB31364@frosties>
2015-09-24  6:30   ` [fuse-devel] " Miklos Szeredi
2015-09-24 19:17 ` Ashish Samant
2015-09-25 12:11   ` Miklos Szeredi [this message]
2015-09-25 17:53     ` Ashish Samant
2015-09-29  6:18     ` Srinivas Eeda

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=CAJfpegsgjV2ePkdjZDAi5GoJ5M-Zeoy10v-5p+bzyHVAnGQpuA@mail.gmail.com \
    --to=miklos@szeredi.hu \
    --cc=ashish.samant@oracle.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.eeda@oracle.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).