linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Elisseev <vovan@vovan.nl>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS3 + kerberos: performance issues
Date: Wed, 08 Jun 2011 08:26:17 +0200	[thread overview]
Message-ID: <1307514377.1533.35.camel@vovan.net.home> (raw)
In-Reply-To: <20110607230754.GF13911@fieldses.org>

All of the accounts, except very limited amount, are in LDAP, and as I
can see user information is identical on server and client. As for my
tests, below are all the details. Difference in speed while copying a
lot of small files is _huge_... I'd appreciate if somebody more familiar
with NFS/kerberos combination can provide a kind of explanation. 

Regards,
Vlad.

* Local directory is /mnt/data/tmp/coreboot/src
# find x86/ | wc -l
296
# du -csh x86
1.5M	x86
1.5M	total
* First try without kerberos: grep /mnt/tmp/ /proc/mounts
nfs:/mnt/tmp /mnt/tmp nfs
rw,noatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.219,mountvers=3,mountport=32767,mountproto=tcp,local_lock=none,addr=192.168.1.219 0 0
# time cp -i -arv /mnt/data/tmp/coreboot/src/arch/x86 /mnt/tmp/x86 
cp -i -arv /mnt/data/tmp/coreboot/src/arch/x86 /mnt/tmp/x86 0.01s user
0.04s system 10% cpu 0.476 total

* Second try with kerberos: grep /mnt/tmp/ /proc/mounts
nfs:/mnt/tmp /mnt/tmp nfs
rw,noatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=krb5,mountaddr=192.168.1.219,mountvers=3,mountport=32767,mountproto=tcp,local_lock=none,addr=192.168.1.219 0 0
# time cp -i -arv /mnt/data/tmp/coreboot/src/arch/x86 /mnt/tmp/x86 
cp -i -arv /mnt/data/tmp/coreboot/src/arch/x86 /mnt/tmp/x86  0.01s user
0.07s system 0% cpu 23.294 total

At the same time test with a single file (621M):
* without kerberos: 
cp -i -av /mnt/media/images/GNOME_3.x86_64-0.2.0-Build1.1.iso   0.00s
user 0.69s system 5% cpu 13.521 total
* with kerberos:
cp -i -av /mnt/media/images/GNOME_3.x86_64-0.2.0-Build1.1.iso   0.00s
user 0.55s system 2% cpu 26.299 total

With the same file, but with "dd
if=/mnt/media/images/GNOME_3.x86_64-0.2.0-Build1.1.iso
of=/mnt/tmp/test.iso bs=32M"
gives:
* without kerberos: 651165696 bytes (651 MB) copied, 10.7168 s, 60.8
MB/s
* with kerberos: 651165696 bytes (651 MB) copied, 24.6176 s, 26.5 MB/s


On Tue, 2011-06-07 at 19:07 -0400, J. Bruce Fields wrote:
> On Fri, Jun 03, 2011 at 07:57:16PM +0200, Vladimir Elisseev wrote:
> > There's no mount command involved in timing. It's simply copy of the
> > same directory (with many small files to NFS share with and without
> > sec=krb5 mount option.
> 
> Weird.
> 
> I wonder if the krb5 principal is being mapped to a different user on
> the server side, and that's making some difference.
> 
> Still, could you give us the full details?  (Exactly what commands are
> you running, what results do you see?)
> 
> --b.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2011-06-08  8:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03  7:29 NFS3 + kerberos: performance issues Vladimir Elisseev
2011-06-03 12:32 ` Trond Myklebust
2011-06-03 17:57   ` Vladimir Elisseev
2011-06-07 23:07     ` J. Bruce Fields
2011-06-08  6:26       ` Vladimir Elisseev [this message]
2011-06-08 15:39         ` J. Bruce Fields
2011-06-08 16:00           ` Vladimir Elisseev
2011-06-08 16:24             ` J. Bruce Fields
2011-06-09  5:02               ` Vladimir Elisseev
2011-06-09 11:34                 ` J. Bruce Fields

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=1307514377.1533.35.camel@vovan.net.home \
    --to=vovan@vovan.nl \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    /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).