You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2013/10/31 16:41:21 UTC
[jira] [Updated] (CASSANDRA-6278) Use AtomicIntegerFieldUpdater to
save memory in row cache
[ https://issues.apache.org/jira/browse/CASSANDRA-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson updated CASSANDRA-6278:
---------------------------------------
Attachment: 0001-Use-AtomicIntegerFieldUpdater-to-save-memory-in-row-.patch
> Use AtomicIntegerFieldUpdater to save memory in row cache
> ---------------------------------------------------------
>
> Key: CASSANDRA-6278
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6278
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Trivial
> Fix For: 2.1
>
> Attachments: 0001-Use-AtomicIntegerFieldUpdater-to-save-memory-in-row-.patch
>
>
> from this:
> http://normanmaurer.me/blog/2013/10/28/Lesser-known-concurrent-classes-Part-1/
> instead of having an AtomicInteger, we can keep a volatile int and use AtomicIntegerFieldUpdater to atomically update the value
--
This message was sent by Atlassian JIRA
(v6.1#6144)