You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "刘珍 (Jira)" <ji...@apache.org> on 2021/11/24 08:32:00 UTC

[jira] [Commented] (IOTDB-1895) Cache leader optimization for batch write interfaces on multiple devices

    [ https://issues.apache.org/jira/browse/IOTDB-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17448443#comment-17448443 ] 

刘珍 commented on IOTDB-1895:
---------------------------

PASS. [^SessionExample.java] 
rc2 session:
real    0m20.598s
rc1 session:
real    0m37.477s


> Cache leader optimization for batch write interfaces on multiple devices
> ------------------------------------------------------------------------
>
>                 Key: IOTDB-1895
>                 URL: https://issues.apache.org/jira/browse/IOTDB-1895
>             Project: Apache IoTDB
>          Issue Type: Improvement
>            Reporter: Xinyu Tan
>            Assignee: Quan Siyi
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: SessionExample.java
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> At present, the cache leader performance optimization for distributed write performance is critical ([the design document|https://shimo.im/docs/dYwjwtrTPXPWcqxj]) . Although the current implementation in the session module for all equipment cache handling, On the server side, however, only writes to a single device are passed clues, causing the partition cache of the batch interface to be effectively invalidated. As the number of users of multi-device interfaces increases, we need to do this optimization.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)