[jira] [Updated] (IGNITE-29169) Use CopyOnWriteIntMap for rarely updated maps on cache hot paths

["Nikita Amelchev (Jira)" <ji...@apache.org>]

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

Nikita Amelchev updated IGNITE-29169:
-------------------------------------
    Fix Version/s: 2.19

> Use CopyOnWriteIntMap for rarely updated maps on cache hot paths
> ----------------------------------------------------------------
>
>                 Key: IGNITE-29169
>                 URL: https://issues.apache.org/jira/browse/IGNITE-29169
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Nikita Amelchev
>            Assignee: Nikita Amelchev
>            Priority: Minor
>             Fix For: 2.19
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Several int-keyed maps that are read on the cache operation path but updated only when a cache or a cache group starts or stops still pay for concurrent writes on every read: the per-partition entry and size maps of shared cache groups take a read-write lock on each access, {{DataRegionMetricsImpl}} keeps a hand-written copy-on-write map guarded by its own lock, and the affinity key field cache boxes the type ID on every lookup. This is exactly the read-mostly case {{CopyOnWriteIntMap}} from IGNITE-29099 was introduced for, so these maps should use it instead of their own locking and copying.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)