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

Posted to dev@iotdb.apache.org by "xiangdong Huang (JIRA)" <ji...@apache.org> on 2019/06/02 05:00:03 UTC

[jira] [Created] (IOTDB-111) [Discuss] Can we improve the performance of Thrift RPC in IoTDB

xiangdong Huang created IOTDB-111:
-------------------------------------

             Summary: [Discuss] Can we improve the performance of Thrift RPC in IoTDB
                 Key: IOTDB-111
                 URL: https://issues.apache.org/jira/browse/IOTDB-111
             Project: Apache IoTDB
          Issue Type: Wish
            Reporter: xiangdong Huang


Hi, 

according to some experiments, I find that if there are many concurrent clients (more than 500 connections) connecting to IoTDB, the performance is not as good as what we expect.

Maybe, we can consider whether we have fully exploited the performance of Thrift...

E.g., Thrift provides 5 modes:

[· TSimpleServer
· TNonblockingServer
· THsHaServer
· TThreadedSelectorServer
· TThreadPoolServer|https://liyonghui160com.iteye.com/blog/2088945]

Now we are using the last one, [TThreadPoolServer|https://liyonghui160com.iteye.com/blog/2088945]. I do not know whether it is the best one for us.  Experiments and result data is needed.

 

Thrift experts are welcomed to show your suggestion. 

Other contributors are also welcomed to bench the different implementations. :)

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)