You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Nick Hill (JIRA)" <ji...@apache.org> on 2018/02/20 04:04:00 UTC

[jira] [Updated] (CURATOR-447) TreeCache: Improve memory usage and concurrent update logic

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

Nick Hill updated CURATOR-447:
------------------------------
    Fix Version/s: 4.0.2

> TreeCache: Improve memory usage and concurrent update logic
> -----------------------------------------------------------
>
>                 Key: CURATOR-447
>                 URL: https://issues.apache.org/jira/browse/CURATOR-447
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>    Affects Versions: 3.3.0, 2.12.0, 4.0.1
>            Reporter: Nick Hill
>            Priority: Minor
>              Labels: performance, stability
>             Fix For: 4.0.2
>
>
> Jira https://issues.apache.org/jira/browse/CURATOR-374 reduced per-node memory usage in {{TreeCache}}. It can be improved further via removal of the {{nodeState}} field - its {{LIVE}} state corresponds exactly to the adjacent {{childData}} field being non-null, and a sentinel {{ChildData}} value can be used for the {{DEAD}} state. This simplification also reduces the room for bugs and state inconsistencies.
> Other improvements included:
> * A further simplification to have {{TreeNode}} extend {{AtomicReference}}, which obviates the need for an explicit {{childData}} field
> * More robust cache update logic (in get-children and get-data event callbacks)
> * Avoid overhead of incrementing/decrementing the {{outstandingOps}} atomic integer post-initialization



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)