Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <6050823.194341284516093719.JavaMail.jira@thor>
Date: Tue, 14 Sep 2010 22:01:33 -0400 (EDT)
From: "T Jake Luciani (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-1267) Improve performance of cached row
 slices
In-Reply-To: <16593555.315761278863989523.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

T Jake Luciani updated CASSANDRA-1267:
--------------------------------------

    Comment: was deleted

(was: FYI, This didn't make it into 0.7-beta1 somehow)

> Improve performance of cached row slices
> ----------------------------------------
>
>                 Key: CASSANDRA-1267
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1267
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>            Priority: Minor
>             Fix For: 0.7 beta 1
>
>         Attachments: 1267-v2.txt, 1267-v3.txt, cached-row-slice-perf-patch-1.txt
>
>
> In Lucandra, I have a use case to pull all columns for a given row.  
> I've noticed that for rows with large numbers of columns this takes much longer than I would think since row caching is enabled.
> After looking into this I see that the cached row is rebuilt and pruned even though I want all columns.  
> This patch skips this use case and in my case has improved performance significantly.
> From ~400ms to ~50ms

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.