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

ASF GitHub Bot commented on CURATOR-374:
----------------------------------------

GitHub user swallez opened a pull request:

    https://github.com/apache/curator/pull/185

    CURATOR-374: Replace AtomicReferences by AtomicFieldUpdaters to save 
allocations

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/swallez/curator master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/185.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #185
    
----
commit 2ae72d67a499c92a6ca0bea795d28b13b54d8b0c
Author: Sylvain Wallez <[email protected]>
Date:   2017-01-04T10:47:32Z

    CURATOR-374: Replace AtomicReferences by AtomicFieldUpdaters to save 
allocations

----


> Reduce memory usage in TreeCache
> --------------------------------
>
>                 Key: CURATOR-374
>                 URL: https://issues.apache.org/jira/browse/CURATOR-374
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>    Affects Versions: 3.2.1
>            Reporter: Sylvain Wallez
>            Assignee: Scott Blum
>            Priority: Minor
>
> TreeCache uses 3 {{AtomicReference}} objects in its tree nodes to ensure 
> atomic updates. On large trees (we have 1M nodes) this can cause a 
> significant memory overhead.
> Using {{volatile}} fields with a {{AtomicReferenceFieldUpdater}} would avoid 
> this while keeping the atomicity garantees.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to