[
https://issues.apache.org/jira/browse/GEODE-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367027#comment-15367027
]
ASF GitHub Bot commented on GEODE-1587:
---------------------------------------
GitHub user nabarunnag opened a pull request:
https://github.com/apache/incubator-geode/pull/191
GEODE-1587: Replaced AtomicInteger with AtomicIntegerFieldUpdater
* Use of AtomicIntegerFieldUpdater decereased the memory overhead
per entry during index creation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nabarunnag/incubator-geode feature/GEODE-1587
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-geode/pull/191.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 #191
----
commit 782ffb61f318d2809117ea76124b5065725b7537
Author: nabarun <n...@pivotal.io>
Date: 2016-06-27T17:25:20Z
GEODE-1587: Replaced AtomicInteger with AtomicIntegerFieldUpdater
* Use of AtomicIntegerFieldUpdater decereased the memory overhead
per entry during index creation
----
> Replace AtomicInteger with AtomicIntegerFieldUpdater in AbstractIndex.java
> --------------------------------------------------------------------------
>
> Key: GEODE-1587
> URL: https://issues.apache.org/jira/browse/GEODE-1587
> Project: Geode
> Issue Type: Bug
> Reporter: nabarun
>
> Use of Atomic Integer instead of volatile int resulted in an increase in the
> memory overhead per index entry by 8 bytes. It is suggested that use of
> AtomicIntegerFieldUpdater for atomic operations on a volatile int results in
> a decrease in the memory overhead per index entry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
