cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan King (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-678) row-level cache
Date Mon, 11 Jan 2010 18:06:54 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798751#action_12798751
] 

Ryan King commented on CASSANDRA-678:
-------------------------------------

Configuring it by rows would be fine. Most of our rows will be pretty consistently sized (within
a given CF) so we can do the math to get GB's.

> row-level cache
> ---------------
>
>                 Key: CASSANDRA-678
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-678
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.9
>
>         Attachments: 0001-basic-caching.txt, 0002-clean-up-onstart-to-fix-cache-size-calculation.txt,
0003-instrumentation.txt, 0004-make-rowcache-keycache-configurable-per-CF.txt, 0005-combine-SSTable-keycaches-into-one-at-CFS-level.-do-no.txt,
0005-update-cached-rows-in-place-instead-of-invalidating-.patch
>
>
> We have a key cache but that doesn't help mitigate the expensive deserialization of the
actual data to return.
> Adding a row-level cache should be fairly simple using a ConcurrentLinkedHashMap<String
[key], ColumnFamily> structure.  (We will only cache whole rows at a time, since already
know how to query on those in-memory.  This limits us to CFs full of narrow rows but that
is a common enough use case to be worth tackling if it can be done simply enough.)

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