[
https://issues.apache.org/jira/browse/IOTDB-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jialin Qiao closed IOTDB-98.
----------------------------
Resolution: Done
> Batch insertion in Server
> -------------------------
>
> Key: IOTDB-98
> URL: https://issues.apache.org/jira/browse/IOTDB-98
> Project: Apache IoTDB
> Issue Type: Improvement
> Reporter: Jialin Qiao
> Priority: Minor
>
> Currently, when the client sends a batch of statements (insert/delete) to the
> server, the server will get each statement from the batch and execute one by
> one. For each statement, the corresponding FileNodeProcessor (for a storage
> group) will get a write lock and then execute the statement, which causes
> unnecessary lock contention.
> It can be improved by getting a write lock once and executing a batch of
> statements. We can first consider the scenario that the statements in a batch
> are all insertions.
> The new process mainly contains 3 steps:
> (1) Group the insert statement by storage group while retaining the original
> order in the batch.
> (2) For each storage group, get the write lock and execute all statements
> belong to it.
> (3) Set the return code of each statement to the origin position in the batch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
