[
https://issues.apache.org/jira/browse/CASSANDRA-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267349#comment-13267349
]
Pavel Yaskevich commented on CASSANDRA-3762:
--------------------------------------------
Why don't you serialize data (payload) of the caches, which is the main goal of
this ticket? CacheSerializer should serialize the *whole* cache entry - key +
payload, that way we would minimize the time taken for processing on
deserialize (aka when caches are loaded) and ColumnFamilyStore wouldn't be
involved in the deserialization process fo the updated cache and you won't have
to make methods such as getTopLevelColumns public. Also you forgot to force
cache flush upon system shutdown as I wrote in my previous comment.
> AutoSaving KeyCache and System load time improvements.
> ------------------------------------------------------
>
> Key: CASSANDRA-3762
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3762
> 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-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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
