You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Xiangdong Huang (Jira)" <ji...@apache.org> on 2021/02/20 04:37:00 UTC
[jira] [Commented] (IOTDB-1163) Optimize the insertion speed of
insertRecords interface in Session
[ https://issues.apache.org/jira/browse/IOTDB-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287500#comment-17287500 ]
Xiangdong Huang commented on IOTDB-1163:
----------------------------------------
make sense. +1
> Optimize the insertion speed of insertRecords interface in Session
> ------------------------------------------------------------------
>
> Key: IOTDB-1163
> URL: https://issues.apache.org/jira/browse/IOTDB-1163
> Project: Apache IoTDB
> Issue Type: Improvement
> Reporter: Houliang Qi
> Assignee: Houliang Qi
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.12.0
>
> Attachments: image-2021-02-20-12-00-14-296.png, image-2021-02-20-12-07-05-448.png
>
>
> At present, the insertRecords interface generates an InsertRowPlan for each record of data. In this way, a raft log will be generated in the cluster version. Because every raft log will be locked, it will bring a lot of overhead.
> At the same time, if some records belong to the same raft replication group, they can be sent to other nodes of this raft group as a raft log, which will reduce the transmission of RPC.
> For example, 10 records belong to the same raft replication group. If the 10 records are regarded as a raft log, one node needs one RPC. If each log is regarded as a raft log, it needs 10 RPCs.
>
> And we use iotdb-benchmark to test the insertRecords interface, we can see that, after optimization, the performance is improved by 13 times.
> !image-2021-02-20-12-07-05-448.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)