cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1267) Improve performance of cached row slices
Date Sat, 17 Jul 2010 01:33:49 GMT

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

Jonathan Ellis updated CASSANDRA-1267:
--------------------------------------

    Attachment: 1267-v3.txt

bq. I thought the logic was redundant QueryFilter.isRelevant

the difference is, isRelevant needs to keep still-active tombstones, but those don't count
for what the client sees

bq. IColumn c = cf.getColumnsMap().get(cname);

ah, right, I meant to keep that change but forgot when I was moving code around.  v3 attached.

> 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
>
>         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.


Mime
View raw message