[ https://issues.apache.org/jira/browse/IOTDB-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jialin Qiao closed IOTDB-97. ---------------------------- Fix Version/s: 0.9.0 Resolution: Fixed > Try compression in RPC > ---------------------- > > Key: IOTDB-97 > URL: https://issues.apache.org/jira/browse/IOTDB-97 > Project: Apache IoTDB > Issue Type: Improvement > Reporter: Jialin Qiao > Priority: Minor > Fix For: 0.9.0 > > > When executing a batch insertion in JDBC with many insert statements (e.g., > >1000), the message to be transferred will be very large. The write > throughput may be improved by compressing the message transferred between > client and server. > Currently, thrift is used in RPC. The protocol we use is TBinaryProtocol > which does not compact the data that transferred. There are two ways to > improve: > (1) Use TCompactProtocol instead of TBinaryProtocol. There are two classes > need to be modified: JDBCService and IoTDBConnection. This protocol will > compress the data in each RPC, I'm not sure whether this protocol is better > when the size of transferred data is small. > (2) We can just compress the data in executeBatch when the batch_size reaches > a threshold. Add a compressed string that stores the SQLs in IoTDBStatement > and use a flag to determine whether this field is used. -- This message was sent by Atlassian Jira (v8.3.2#803003)