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 0ABD010A29 for ; Wed, 30 Apr 2014 00:57:58 +0000 (UTC) Received: (qmail 45586 invoked by uid 500); 30 Apr 2014 00:57:39 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 45354 invoked by uid 500); 30 Apr 2014 00:57:32 -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 45253 invoked by uid 99); 30 Apr 2014 00:57:29 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Apr 2014 00:57:29 +0000 Date: Wed, 30 Apr 2014 00:57:29 +0000 (UTC) From: "Ryan McGuire (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-5937) check read performance between 1.2.5 and 1.2.8 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-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McGuire updated CASSANDRA-5937: ------------------------------------ Labels: qa-resolved (was: ) > check read performance between 1.2.5 and 1.2.8 > ---------------------------------------------- > > Key: CASSANDRA-5937 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5937 > Project: Cassandra > Issue Type: Test > Reporter: Chris Burroughs > Assignee: Ryan McGuire > Priority: Minor > Labels: qa-resolved > > We upgraded from 1.2.5 to 1.2.8 on 08-02 and saw a significant increase in read latency: > * median: < 1ms to > 1ms > * 75p: ~ 1 ms to > 3.5 ms > * 95p: ~ 3 ms to ~ 8 ms > Cluster is a 2 DC cluster with about 20 nodes per DC (using GossipingPropertyFileSnitch). All queries are for one Keyspace filled with skinny rows so we have Row cache enabled and the Key cache disabled. The row cache hit is close to 70%, which makes the magnitude of the new median/75th hard to understand. > I have not been able to demonstrate a regression with stress on either a single or dozen node cluster. For internal reasons invovling client side problem we have not tried rolling back so I'm not positive it's a cassandra code problem (as opposed to something else we did/configured). > Thanks for checking it out! -- This message was sent by Atlassian JIRA (v6.2#6252)