You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Jens Geyer (Jira)" <ji...@apache.org> on 2022/09/09 14:19:00 UTC

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

     [ https://issues.apache.org/jira/browse/THRIFT-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Geyer updated THRIFT-5624:
-------------------------------
    Summary: suboptimal performance of the c# named pipe server transport in multithread servers  (was: suboptimal performance of the c# named pipe server in multithread servers)

> suboptimal performance of the c# named pipe server transport in multithread servers
> -----------------------------------------------------------------------------------
>
>                 Key: THRIFT-5624
>                 URL: https://issues.apache.org/jira/browse/THRIFT-5624
>             Project: Thrift
>          Issue Type: Improvement
>          Components: netstd - Library
>            Reporter: Jens Geyer
>            Assignee: Jens Geyer
>            Priority: Major
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)