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

Posted to jira@kafka.apache.org by "Ki Lok Wong (Jira)" <ji...@apache.org> on 2021/05/18 02:45:00 UTC

[jira] [Updated] (KAFKA-12804) In-Memory state store backed by InMemoryKeyValueStore is slow due to synchronizing reads/writes using a single lock.

     [ https://issues.apache.org/jira/browse/KAFKA-12804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ki Lok Wong updated KAFKA-12804:
--------------------------------
    Remaining Estimate: 2h  (was: 2m)
     Original Estimate: 2h  (was: 2m)

> In-Memory state store backed by InMemoryKeyValueStore is slow due to synchronizing reads/writes using a single lock.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-12804
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12804
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 2.6.2
>            Reporter: Ki Lok Wong
>            Priority: Minor
>              Labels: performance, pull-request-available
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Default In-Memory state store (InMemoryKeyValueStore) uses TreeMap as the backing map implementation.  Read/write methods such as get() and put() are synchronized on the same lock hence significantly reducing multi-thread performance.
> https://github.com/a0x8o/kafka/blob/f834be5e73e46805b29df9845bf09be98f91fc09/streams/src/main/java/org/apache/kafka/streams/state/internals/InMemoryKeyValueStore.java#L78



--
This message was sent by Atlassian Jira
(v8.3.4#803005)