Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9949ED906 for ; Fri, 9 Nov 2012 23:51:12 +0000 (UTC) Received: (qmail 65620 invoked by uid 500); 9 Nov 2012 23:51:12 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 65594 invoked by uid 500); 9 Nov 2012 23:51:12 -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 65584 invoked by uid 99); 9 Nov 2012 23:51:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2012 23:51:12 +0000 Date: Fri, 9 Nov 2012 23:51:12 +0000 (UTC) From: "Pavel Yaskevich (JIRA)" To: commits@cassandra.apache.org Message-ID: <1658463138.94579.1352505072437.JavaMail.jiratomcat@arcas> In-Reply-To: <1513990058.90216.1352436373333.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (CASSANDRA-4937) CRAR improvements (object cache + CompressionMetadata chunk offset storage moved off-heap). 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-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494441#comment-13494441 ] Pavel Yaskevich commented on CASSANDRA-4937: -------------------------------------------- bq. Still don't like the global objectCache code. SSTR queue (no Map) would be better. Or, what about SSTR Threadlocal? The reason why it's done via queues associated with filenames is that we want to get rid of CRAR instances as soon as we done with individual SSTables and I don't want to involve SSTR there more then just cleaning queues upon termination. bq. Isn't the right fix then to only drop the recently-read blocks during sequential i/o? We can't because it would require (e.g. compaction) to know of how something is using files, it could remove cache from somebody's fit anyway and we would use too many system calls if we do that. > CRAR improvements (object cache + CompressionMetadata chunk offset storage moved off-heap). > ------------------------------------------------------------------------------------------- > > Key: CASSANDRA-4937 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4937 > Project: Cassandra > Issue Type: Improvement > Affects Versions: 1.1.6 > Reporter: Pavel Yaskevich > Assignee: Pavel Yaskevich > Priority: Minor > Fix For: 1.1.7 > > Attachments: CASSANDRA-4937.patch > > > After good amount of testing on one of the clusters it was found that in order to improve read latency we need to minimize allocation rate that compression involves, that minimizes GC (as well as heap usage) and substantially decreases latency on read heavy workloads. > I have also discovered that RAR skip cache harms performance in situation when reads are done in parallel with compaction working with relatively big SSTable files (few GB and more). The attached patch removes possibility to skip cache from compressed files (I can also add changes to RAR to remove skip cache functionality as a separate patch). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira