cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13508) Make system.paxos table compaction strategy configurable
Date Sat, 20 May 2017 16:35:04 GMT


Blake Eggleston commented on CASSANDRA-13508:

Thinking about this a bit more, TWCS might be a better choice in some workloads. LCS should
be the best choice when you have a table where the keys have regular activity on them over
a long period of time. For workloads where you're just using paxos as a step in something
like a user signup process though, where you're not likely to have multiple hits on the same
user over time, TWCS could be a better choice.

> Make system.paxos table compaction strategy configurable
> --------------------------------------------------------
>                 Key: CASSANDRA-13508
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jay Zhuang
>            Assignee: Jay Zhuang
>             Fix For: 4.0, 4.x
>         Attachments: test11.png, test2.png
> The default compaction strategy for {{system.paxos}} table is LCS for performance reason:
CASSANDRA-7753. But for CAS heavily used cluster, the system is busy with {{system.paxos}}
> As the data in {{paxos}} table are TTL'ed, TWCS might be a better fit. In our test, it
significantly reduced the number of compaction without impacting the latency too much:
> !test11.png!
> The time window for TWCS is set to 2 minutes for the test.
> Here is the p99 latency impact:
> !test2.png!
> the yellow one is LCS, the purple one is TWCS. Average p99 has about 10% increase.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message