From: Martin Knoblauch <knobi@knobisoft.de>
To: nfs@lists.sourceforge.net
Subject: Strange performance problems between Linux client and Sun/Solaris-10 Server with SAM-FS
Date: Mon, 14 May 2007 04:14:10 -0700 (PDT) [thread overview]
Message-ID: <758936.68723.qm@web32601.mail.mud.yahoo.com> (raw)
Hi,
we are fighting with a strange performance problem when accessing a
Sun/Solaris-10 server from a Linux NFS client (HP DL380G4, x86_64,
RHEL4U3 user-space, various kernels from 2.6.9-34.ELsmp up to
2.9.21.1).
The underlying FS on the Sun is SAM-FS (4.5.33) which provides HSM
capabilities. The basic layout is that the "online cache" is relatively
small on "high-speed" FC disks, while the offline data are stored on
cheapish SATA disks and high-speed tapes.
The problem arises when accessing (reading) a file that is offline on
the Sun. In this case the so-called "stager" brings it back to the
online-cache first, while the client waits for the data to be
available.
This works fine (staging speed up-to or larger 50 MB/sec) on:
- administrative "stage" request
- accessing the offline file on the Sun-Server itself
- accessing the offline file from a Solaris-10 NFS client
When doing the same from the Linux Client performance drops below 10
MB/sec. Network performance itself looks good when accessing the file
"online".
One thing that looks different when doing tcpdump/snoop traces between
the systems is that in the Linux/Solaris case the client seems to send
more READ3 requests (factor > 3) that the Server acknowledges (both in
the online and offline case). In the Solaris/Solaris case the number of
requests and acknowledgements is about the same.
The remote filesystem is mounted NFS3/TCP with the following
parameters:
xxxx:/net/xxxx/fs03 on /net/xxxx/fs03 type nfs
(rw,hard,intr,bg,nfsvers=3,proto=tcp,timeo=600,rsize=32768,wsize=32768,addr=yy.yy.yy.yy)
We are already talking to the Sun people, but they cannot reproduce.
So I put my hope for some insight on this list.
Cheers
Martin
PS: Please CC me on replies, as I am only getting the digest
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-05-14 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 11:14 Martin Knoblauch [this message]
2007-05-14 14:20 ` Strange performance problems between Linux client and Sun/Solaris-10 Server with SAM-FS Martin Knoblauch
2007-05-14 14:39 ` Talpey, Thomas
2007-05-14 16:45 ` Martin Knoblauch
2007-05-14 16:58 ` Talpey, Thomas
2007-05-14 17:28 ` Chuck Lever
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=758936.68723.qm@web32601.mail.mud.yahoo.com \
--to=knobi@knobisoft.de \
--cc=nfs@lists.sourceforge.net \
/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