linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Frank Filz" <ffilzlnx@mindspring.com>
To: "'Benjamin Coddington'" <bcodding@redhat.com>,
	"'Pankaj Singh'" <psingh.ait@gmail.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: RE: Tool or module to test NFSv3 server scalability
Date: Fri, 25 Sep 2015 15:00:18 -0700	[thread overview]
Message-ID: <028f01d0f7dd$91c11e50$b5435af0$@mindspring.com> (raw)
In-Reply-To: <alpine.OSX.2.19.9992.1509250914050.24831@planck.local>

> > Hi all,
> >
> > I am new to nfs. I have a requirement to test the scalability of NFSv3.
> > To test this I would require a solution that can simulate multiple nfs
clients.
> > As its known a single TCP connection is used for communication between
> > client and server. So to increase multiple connections multiple
> > nfs-clients would be needed. Which is very costly.
> >
> > So would need some method/tool to create multiple nfs TCP connections
> > from single or few machines.
> 
> 
> Hi Pankaj, this is a fun question.
> 
> One thought I had would be to use a big block ip addresses on a linux NFS
> server, and mount the filesystem with each unique server ip address.  That
> should create a bunch of connections with only a single client and server.
> IPv6 is ideal since there's a lot of address room.
> 
> This turns out to be really easy to do if you have a linux server with
Any-IP
> support [1].
> 
> On my server, I set up a rule so that any ipv6 traffic arriving on eth0
consults
> route table 200, and set up route table 200 to route everything to the
> loopback interface:
> 
> ip -6 rule add from all iif eth0 lookup 200 ip -6 route add local default
dev lo
> table 200
> 
> Then on my client, I set a routing rule for a large local network to route
to my
> server's eth0 ipv6 real-world address:
> 
> ip -6 route add fd12:3456:789a:1::/64 via
> 2601:18b:4000:1a2a:5054:ff:fe30:a648
> 
> Now, whenever my client sends any traffic to any ip in
fd12:3456:789a:1::/64,
> it will go to my server's loopback adapter which should accept it as
though it
> had that address.
> 
> On the client we can then bash out some mounts:
> 
> for j in {1..1024}; do mkdir /mnt/v6/$(printf %x $j); done; cd /mnt/v6 for
dir in
> *; do mount \[fd12:3456:789a:1::$dir\]:/ $dir; done grep fd12 /proc/mounts
|
> wc
>    1024    6144  248022
> 
> This should cause the linux nfs client's rpc code to create a separate
> connection for each mount.

You can also do something like this using localhost addresses (I often for
testing use several different localhost addresses to simulate multiple
clients).

I used it long ago to check out some stuff with 1000 clients.

Frank


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

      reply	other threads:[~2015-09-25 22:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 11:08 Tool or module to test NFSv3 server scalability Pankaj Singh
2015-09-25 13:29 ` Benjamin Coddington
2015-09-25 22:00   ` Frank Filz [this message]

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='028f01d0f7dd$91c11e50$b5435af0$@mindspring.com' \
    --to=ffilzlnx@mindspring.com \
    --cc=bcodding@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=psingh.ait@gmail.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).