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 C86D1F2C2 for ; Tue, 2 Apr 2013 16:51:16 +0000 (UTC) Received: (qmail 74996 invoked by uid 500); 2 Apr 2013 16:51:16 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 74975 invoked by uid 500); 2 Apr 2013 16:51:16 -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 74944 invoked by uid 99); 2 Apr 2013 16:51:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Apr 2013 16:51:15 +0000 Date: Tue, 2 Apr 2013 16:51:15 +0000 (UTC) From: "Vijay (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-4860) Estimated Row Cache Entry size incorrect (always 24?) 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-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay updated CASSANDRA-4860: ----------------------------- Attachment: 4860-perf-test.zip Ryan, Micro benchmark shows v3 is better, is there any chance you are hitting the same key in the key cache often? The reason for asking is that you might have a smaller key cache since the calculation is more accurate. If yes then i would increase the keycache and try. To be clear the Meter.measure() is bug and cannot be used in production and can cause OOM. > Estimated Row Cache Entry size incorrect (always 24?) > ----------------------------------------------------- > > Key: CASSANDRA-4860 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4860 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 1.1.0, 1.2.3, 2.0 > Reporter: Chris Burroughs > Assignee: Vijay > Fix For: 1.2.0 beta 3 > > Attachments: 0001-4860-v2.patch, 0001-4860-v3.patch, 0001-CASSANDRA-4860-for-11.patch, 0001-CASSANDRA-4860.patch, 4860-perf-test.zip, trunk-4860-revert.patch > > > After running for several hours the RowCacheSize was suspicious low (ie 70 something MB) I used CASSANDRA-4859 to measure the size and number of entries on a node: > In [3]: 1560504./65021 > Out[3]: 24.0 > In [4]: 2149464./89561 > Out[4]: 24.0 > In [6]: 7216096./300785 > Out[6]: 23.990877204647838 > That's RowCacheSize/RowCacheNumEntires . Just to prove I don't have crazy small rows the mean size of the row *keys* in the saved cache is 67 and Compacted row mean size: 355. No jamm errors in the log > Config notes: > row_cache_provider: ConcurrentLinkedHashCacheProvider > row_cache_size_in_mb: 2048 > Version info: > * C*: 1.1.6 > * centos 2.6.32-220.13.1.el6.x86_64 > * java 6u31 Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode) -- 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