cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-801) The Key Cache should be configurable by absolute numbers
Date Fri, 26 Feb 2010 03:48:27 GMT


Jonathan Ellis commented on CASSANDRA-801:

cleaned out old patches, combined patches 1 and 2 and 3,4,6, and did a bunch of cleanup.

    Migrate rowCache into SSTableTracker and recalculate cache size when sstable collection

    Unify key cache per CF under SSTableTracker, hooked in w/ setTrackedBy replacing addFinalizingReference

    Convert KeysCachedFraction to KeysCached, temporarily breaking things since it gives KeysCached
per SSTable not per CF.  Also refactors how key cache is instantiated, and removes SSTableAccessor
from test suite.  These should be separate patches but I ran out of energy.

> The Key Cache should be configurable by absolute numbers
> --------------------------------------------------------
>                 Key: CASSANDRA-801
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.6
>            Reporter: Ryan King
>            Assignee: Stu Hood
>             Fix For: 0.6, 0.7
>         Attachments: 0001-Convert-KeysCachedFraction-to-KeysCached-temporarily-b.txt,
0002-Unify-key-cache-per-CF-under-SSTableTracker-hooked-in-.txt, 0003-Migrate-rowCache-into-SSTableTracker-and-recalculate-c.txt
> Just like the row cache, the key cache should be configurable by absolute numbers (not
just a fraction). It would be nice to configure it by either memory size or entries (like
the row cache).

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

View raw message