cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3762) AutoSaving KeyCache and System load time improvements.
Date Thu, 03 May 2012 22:40:48 GMT


Vijay updated CASSANDRA-3762:

    Attachment: 0001-CASSANDRA-3762-v5.patch

>>> It means that the method don't return what what it should and should be renamed
to *estimate*SerializedSize but as we would to the same for all of the rows in the cache I
don't see how it would harm LRU if we do the real calculation.
If you are getting hot n keys, it will be making hot keys even more hotter.... renamed.

>>> It does not
the idea is that the newer cache will delete the older one :) so it is a no op after that....
anyways fixed it just for the sake of it :)

>>> What about this one?
As we are using estimate not the real value we need to use the serializedSize.... Thats how
it was earlier too :)
> AutoSaving KeyCache and System load time improvements.
> ------------------------------------------------------
>                 Key: CASSANDRA-3762
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.2
>         Attachments: 0001-CASSANDRA-3762-v2.patch, 0001-CASSANDRA-3762-v3.patch, 0001-CASSANDRA-3762-v4.patch,
0001-CASSANDRA-3762-v5.patch, 0001-SavedKeyCache-load-time-improvements.patch
> CASSANDRA-2392 saves the index summary to the disk... but when we have saved cache we
will still scan through the index to get the data out.
> We might be able to separate this from SSTR.load and let it load the index summary, once
all the SST's are loaded we might be able to check the bloomfilter and do a random IO on fewer
Index's to populate the KeyCache.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message