Return-Path: Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: (qmail 13635 invoked from network); 30 Jan 2011 19:00:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Jan 2011 19:00:07 -0000 Received: (qmail 3352 invoked by uid 500); 30 Jan 2011 19:00:06 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 3273 invoked by uid 500); 30 Jan 2011 19:00:06 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 3265 invoked by uid 99); 30 Jan 2011 19:00:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Jan 2011 19:00:05 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Jan 2011 19:00:05 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p0UIxi0A004551 for ; Sun, 30 Jan 2011 18:59:45 GMT Message-ID: <10506608.296041296413984678.JavaMail.jira@thor> Date: Sun, 30 Jan 2011 13:59:44 -0500 (EST) From: "Vijay (JIRA)" To: commits@cassandra.apache.org Subject: [jira] Commented: (CASSANDRA-1969) Use BB for row cache - To Improve GC performance. In-Reply-To: <31357044.296951294783667007.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988632#action_12988632 ] Vijay commented on CASSANDRA-1969: ---------------------------------- Thanks Jonathan, This indeed looks cleaner than allocateDirect.... wasnt aware of jna.Memory earlier.... Regarding "and allocation is O(N)" --- It provides O(1) as it is backed by Queue and HashMap (which can have maximum of Integer.Max elements in HM) ... the idea was to reduce the number of operations while write..... With the assumption that the GC will cleanup the WeekReference immediately, and wont grow or fragment.... +1 for Jonathan's approach.... > 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-implement-SerializingCache.txt, 0002-Update_existing-1965.txt, 0003-New_Cache_Providers-1969.txt, 0004-TestCase-1969.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. - You can reply to this email to add a comment to the issue online.