You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Goffinet (JIRA)" <ji...@apache.org> on 2011/01/12 02:40:46 UTC

[jira] Commented: (CASSANDRA-1969) Use BB for row cache - To Improve GC performance.

    [ https://issues.apache.org/jira/browse/CASSANDRA-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980494#action_12980494 ] 

Chris Goffinet commented on CASSANDRA-1969:
-------------------------------------------

I am highly in favor of this. +1. This will allow us to separate thread pools on the read path. 1 pool for serving up cached reads, the other for serving up dedicated reads to disk. This is how InnoDB does it. We would no longer have to rely on page cache.

> 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.