On Tue, Sep 18, 2018 at 12:58 PM, Kropelin, Adam <kropelin@amazon.com> wrote:
It allows us to feed more than one tcp stream concurrently. When the tcp stream itself is bandwidth-limited on the client side, and you're using blocking sockets, you have to employ multiple threads. How many threads is enough is the question. 16 isn't enough when you have a fleet of more than that number of bandwidth-limited clients.
The "old crufty" code used up to 200 threads, and that was a configurable limit. We had hit a related stall in 2.0.
And leaves an awful lot of threads waiting.
Yes, that's a down-side with few alternatives other than non-blocking I/O.
Indeed. Matt
--Adam
_______________________________________________ Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
-- Matt Benjamin Red Hat, Inc. 315 West Huron Street, Suite 140A Ann Arbor, Michigan 48103 http://www.redhat.com/en/technologies/storage tel. 734-821-5101 fax. 734-769-8938 cel. 734-216-5309