Single threaded rpcbind is not scalable
In a case there are many (thousands) clients trying to talk with rpcbind in the same time, the single threaded rpcbind will handle the requests sequentially. Since the request handling (plus sending the response to the client) is usually much slower than receiving the request, the last arrived request might be serviced after very long time.
To solve this issue we should make the rpcbind multithreaded.
Updated by Electric Monk about 8 years ago
Author: Marcel Telka <firstname.lastname@example.org> 4575 Single threaded rpcbind is not scalable 4483 rpcbind: Reply for remote calls comes from incorrect UDP port Reviewed by: Ilya Usvyatsky <email@example.com> Reviewed by: Jan Kryl <firstname.lastname@example.org> Reviewed by: Michael Schuster <email@example.com> Reviewed by: Gary Mills <firstname.lastname@example.org> Reviewed by: Jerry Jelinek <email@example.com> Approved by: Robert Mustacchi <firstname.lastname@example.org>