From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.6.xx - NFSv3 vs. Samba Data Transfer Semantics
Date: Sat, 6 Aug 2005 10:34:55 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0508061017150.19178@p34> (raw)
I have three machines with the same motherboard and gigabit ethernet, ABIT
IC7-G.
Two are Linux (Debian)
One is Windows 2000.
When I copy 100 gigabytes from a Windows 2000 PC to either one of my Linux
machines, I get a *SUSTAINED* transfer rate of 40-50MB/s over gigabit.
Sustained meaning, when I watch gkrellm, eth0 never dips below 40MB/s.
When I copy 100 gigabytes from one Linux box to the other over NFS, I see
all sorts of weirdness, 64MB/s for a few seconds, then 40MB/s, then
10-30MB/s, then 0MB/s for 2-3 seconds then 7MB/s, it goes all over the
place. I have tried different (r|w)sizes without any conclusive results,
they do not seem to make much of a difference.
A few examples, copy an ~800MB file to a Linux box:
TCP/FTP:
226 65.484 seconds (measured here), 11.98 Mbytes per second
822514728 bytes received in 65.48 secs (12266.2 kB/s)
UDP/NFSv3:
0.15user 12.00system 0:26.22elapsed 46%CPU (0avgtext+0avgdata
0maxresident)k0inputs+0outputs (0major+148minor)pagefaults 0swaps
0.14user 13.96system 0:28.31elapsed 49%CPU (0avgtext+0avgdata
0maxresident)k0inputs+0outputs (0major+148minor)pagefaults 0swaps
UDP/Samba, Win2K->Linux box:
$ date +%s
1123338368
$ date +%s
1123338399
1123338399 - 1123338368
31 seconds
I suppose NFS makes up for it bursting at such high speeds, but in some
cases, a constant data rate is preferred. Are there any methods to
duplicate the way Samba works to NFS? When NFS transfers are taking
place, watching gkrellm, I see 64MB/s for a few seconds then it goes to 0
as the disk (hda) continues to write for 3-4 seconds, this continues on
and off. With Samba and the W2K box pushing the data, it is more of a
consistent stream with very few delays that are found with NFS.
I am using the Intel e1000 driver for gigabit:
0000:02:01.0 Ethernet controller: Intel Corp. 82547GI Gigabit Ethernet
Controller.
I *do* have the NAPI option enabled for the driver on both Linux machines.
[*] Use Rx Polling (NAPI)
Samba Config:
# Increase overall throughput of samba.
socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=32768 SO_RCVBUF=8192
# Set max xmit size.
max xmit = 8192
NFS Config/fstab Entry:
machine:/mount /local/mount nfs rw,hard,intr,nfsvers=3 0 0
I am using XFS filesystems on both Linux machines. The drives are 7200RPM
Seagate HDDs with either 2MB or 8MB of cache.
Are there any 'tweaks' or 'hacks' to make NFS behave more like Samba or
just to tune it in general that are not commonly known or found on google?
Thanks,
Justin.
next reply other threads:[~2005-08-06 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-06 14:34 Justin Piszcz [this message]
2005-08-07 2:51 ` Greg Banks
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=Pine.LNX.4.63.0508061017150.19178@p34 \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®