[
https://issues.apache.org/jira/browse/CASSANDRA-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980552#action_12980552
]
Ben Manes commented on CASSANDRA-1966:
--------------------------------------
This could be added to CLHM if Cassandra decides its valuable enough and opens
a ticket against the library. The current implementation uses an unspecified
order since this is cheap and the common-case.
Additional ordered API methods could be added. These would be more expensive as
they would require traversing the LRU chain to perform a copy and be a blocking
operation, but would not affect read/write operations.
This example it would be a fair usage and justification of ordered iteration.
Its a trivial change, but its an enhancement I've avoided eagerly performing
until a project considers it a worthwhile feature. If Cassandra's devs think
so, then they can add a feature request.
> Option to control how many items are read on cache load
> -------------------------------------------------------
>
> Key: CASSANDRA-1966
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1966
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Chris Burroughs
>
> CASSANDRA-1417 added an option to save the key and/or row cache keys which is
> cool. However, for a row large cache it can take a long time to read all of
> the rows. For example I have a 400,000 item row cache, and loading that on
> restart takes a little under an hour.
> In addition to configuring the size of the row cache, and how often it should
> be saved to disk, I propose an option to control how many items are loaded on
> startup (or alternately only saving n items out of the full row cache to
> begin with).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
