[
https://issues.apache.org/jira/browse/CASSANDRA-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396263#comment-16396263
]
Lerh Chuan Low commented on CASSANDRA-8460:
-------------------------------------------
Read you loud and clear for stress. I favoured stress because it reports on
operation and latency rates and I didn't want to dig through the code just yet
on what metric exactly stress reports, rather just trusting it as it's the
default cassandra ships with. I do have a custom Java class for doing inserts
and reads (but it doesn't do much beyond that), let me know if you would like
it...? I am also curious what metric you think would be an accurate measure,
off the top of my head from the client side I can think of time from executing
the query to when I receive the answer, but I'm not sure if I could make the
case that the cached version is better compared to the uncached version just
based off that (the alternative is dig through the stress code to look for
more).
I am not very familiar with the low level things in Linux so helping with FIO
will be really appreciated (Doesn't help that my nodes actually run on CoreOS).
I relied on Cloudwatch to verify that my cache is working. When I have time in
the coming days I may write a python script to model TWCS (if you hadn't got to
it then), I agree it should be modeled with TWCS which is why I was trying to
make stress look like it. That said, it was interesting to see if it helped the
other compaction strategies :)
> Make it possible to move non-compacting sstables to slow/big storage in DTCS
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-8460
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8460
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Assignee: Lerh Chuan Low
> Priority: Major
> Labels: doc-impacting, dtcs
> Fix For: 4.x
>
>
> It would be nice if we could configure DTCS to have a set of extra data
> directories where we move the sstables once they are older than
> max_sstable_age_days.
> This would enable users to have a quick, small SSD for hot, new data, and big
> spinning disks for data that is rarely read and never compacted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
