[
https://issues.apache.org/jira/browse/CASSANDRA-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985838#action_12985838
]
Vijay commented on CASSANDRA-1969:
----------------------------------
"Basically it boils down to re-implementing GC at the user level, I think."
Or keeping the JVM smaller and waiting for the GC to cleanup.... I am not sure,
but it might work for cache.... The problem which i have currently is having
the cache invalidate... Currently we get it from cache (For writes) and start
working on that object directly this works for the object cache... but this
might not work for BB cache... hence we might need to add a invalidation
method.
> Use BB for row cache - To Improve GC performance.
> -------------------------------------------------
>
> Key: CASSANDRA-1969
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1969
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: Linux and Mac
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Attachments: BB_Cache-1945.png, JMX-Cache-1945.png,
> Old_Cahce-1945.png, POC-0001-Config-1945.txt,
> POC-0002-Update_existing-1945.txt, POC-0003-New_Cache_Providers-1945.txt
>
>
> Java BB.allocateDirect() will allocate native memory out of the JVM and will
> help reducing the GC pressure in the JVM with a large Cache.
> From some of the basic tests it shows around 50% improvement than doing a
> normal Object cache.
> In addition this patch provide the users an option to choose
> BB.allocateDirect or store everything in the heap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
