From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: <nfs@lists.sourceforge.net>
Subject: RE: ~800 mountpoint limitation
Date: Fri, 17 Oct 2003 12:41:33 -0400 [thread overview]
Message-ID: <16272.7101.893073.601152@charged.uio.no> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C6113127F56@lavender-fe.eng.netapp.com>
>>>>> " " == Charles Lever <Lever> writes:
> i guess i would buy that if someone could convince me the RPC
> client would actually do fair load balancing if given the
> opportunity. my own experience with multi process workloads is
> that we aren't there yet.
Load balancing is a policy problem for the higher levels. The RPC
layer doesn't carry any information about task priorities beyond the
most basic FIFO-style queueing. Why should it?
> in other words, TCP is *designed* to handle network contention,
> so i don't have a problem letting multiple sockets from the
> same client duke it out for network bandwidth.
The slow-start algorithm is not an optimal method for dealing with
contention. Every time you collide, you a forced to growth the
bandwidth linearly from zero up to 1/2 that you initially had before
you collided. After that, you grow using a 1/n rule.
In practice, therefore, you will tend to find it faster if you shunt
everything through the same TCP socket and avoid the collision in the
first place.
Then, with TCP, there's also the issue of reconnections. If the server
starts dropping TCP connections in order to deal with a resource
starvation issue, reconnection is an expensive operation.
IOW: lack of scalability can be a performance problem too...
> i also have some SMP scalability concerns. using a single
> transport means we have many processes on several CPUs that are
> contending for the socket buffer space, the socket and xprt
> locks, and that are holding the BKL while issuing RPCs.
That problem has nothing to do with the issue of multiple sockets or
not. The BKL is held over all RPC calls. I have yet to see numbers
showing that the socket/xprt locks are a major contention problem.
Cheers,
Trond
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-10-17 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 15:09 ~800 mountpoint limitation Lever, Charles
2003-10-17 16:41 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-15 15:46 Ogden, Aaron A.
2003-10-17 17:37 Ogden, Aaron A.
2003-10-14 17:03 Ogden, Aaron A.
2003-10-15 13:01 ` Ian Kent
2003-10-14 16:45 Lever, Charles
2003-10-17 14:55 ` Trond Myklebust
2003-10-14 16:27 Ogden, Aaron A.
2003-10-14 16:44 ` Trond Myklebust
2003-12-15 13:33 ` Ian Kent
2003-10-14 15:51 Ogden, Aaron A.
2003-10-14 16:06 ` Trond Myklebust
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=16272.7101.893073.601152@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=Charles.Lever@netapp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.