[
https://issues.apache.org/jira/browse/CASSANDRA-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-791.
--------------------------------------
Resolution: Duplicate
yes. James, see CASSANDRA-678 and CASSANDRA-688.
> Intelligent RAM Caching
> -----------------------
>
> Key: CASSANDRA-791
> URL: https://issues.apache.org/jira/browse/CASSANDRA-791
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: James Churchman
>
> It should be possibly to predefine what cassandra holds in-momory and what it
> does not, or the priority of data to be cached.
> An example would be a column family that stores huge amount of logs of user
> data, but the user rarely every access that data once it has been inserted.
> The other column family is the login details of each user, probably very tiny
> but all of it accessed hundreds of times day. When the large column family is
> updated i presume that all data healed in ram from the smaller one is
> removed from the ram? it would be preferable that priorities or specific "ram
> quotas" could be assigned to each column family to determine how lightly it
> is for the data to stay in ram. This would mean that memory caching programs
> like mem-cache that have that slightly finer level of control (by allocating
> each individual mem-chache a total amount of ram) would no longer be needed
> and it would simplify system design
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
