[THRIFT-5624] suboptimal performance of the c# named pipe server transport in multithread servers

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.18.0
• Component/s: netstd - Library
• Patch Info: Patch Available
• Assignee: Jens Geyer
• Reporter: Jens Geyer
• Created: 09/Sep/22 14:17
• Updated: 13/Feb/23 21:10
• Resolved: 09/Sep/22 21:00

Description

The netstd TNamedPipeServerTransport may fail to process certain calls, if the client uses a relatively short open pipe timeout, even though we have enough threads ready. Main cause is that the server opens only one server pipe to listen on each time the AcceptImplementationAsync method is called and spends certain time on handling an incoming connection until it listens again.

Issue Links

• links to: GitHub Pull Request #2656