[
https://issues.apache.org/jira/browse/CASSANDRA-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717492#comment-13717492
]
Tyler Hobbs commented on CASSANDRA-5515:
----------------------------------------
bq. If we're not going to take the simple approach with a map, should we keep
more data like this?
That's what I was thinking with the exception of the {{hour_ending_at}} column;
I was thinking we would periodically overwrite a single read count row per
sstable instead of tracking it in time-series fashion. Are you specifically
looking to have both "recent" read rates and total historic read rates? If so,
just using two counters would be lighter weight. I don't foresee compaction
strategies using more than the recent and total rates, but I suppose users
might find full time series data useful.
> Track sstable coldness
> ----------------------
>
> Key: CASSANDRA-5515
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5515
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Tyler Hobbs
> Fix For: 2.0.1
>
> Attachments: 0001-Track-row-read-counts-in-SSTR.patch
>
>
> Keeping a count of reads per-sstable would allow STCS to automatically ignore
> cold data rather than recompacting it constantly with hot data, dramatically
> reducing compaction load for typical time series applications and others with
> time-correlated access patterns. We would not need a separate age-tiered
> compaction strategy.
> (This will really be useful in conjunction with CASSANDRA-5514.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
