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

Voters

Watch issue

Watchers

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 0.18.0
Component/s: netstd - Library
Labels:
None

Patch Info:

Patch Available

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.

Attachments

Issue Links

Add Link

links to

GitHub Pull Request #2656

Delete this link

Activity

Comment

This comment will be Viewable by All Users Viewable by All Users

Cancel

People

Assignee:: Jens Geyer

Reporter:: Jens Geyer

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 09/Sep/22 14:17

Updated:: 13/Feb/23 21:10

Resolved:: 09/Sep/22 21:00

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

suboptimal performance of the c# named pipe server transport in multithread servers