[
https://issues.apache.org/jira/browse/CASSANDRA-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002365#comment-13002365
]
Vijay commented on CASSANDRA-1969:
----------------------------------
Again coming back to the original POC code... where we will reuse the BB's
which are not GC'ed (using weak references) shouldn't that approach work? (if
we are not going to use JNA) i think that way we can guarantee to some extent
that we dont fragment the Direct Memory... Assuming most of our queries results
will be approx of the same size (where chunk size can be defined by the user).
> 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: 0001-Config-1969.txt,
> 0001-introduce-ICache-InstrumentingCache-IRowCacheProvider.txt,
> 0002-Update_existing-1965.txt, 0002-implement-SerializingCache.txt,
> 0002-implement-SerializingCacheV2.txt, 0003-New_Cache_Providers-1969.txt,
> 0003-add-ICache.isCopying-method.txt, 0004-Null-Check-and-duplicate-bb.txt,
> 0004-TestCase-1969.txt, 1969-rollup-and-config.txt, 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
