You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (Jira)" <ji...@apache.org> on 2022/11/16 12:56:00 UTC
[jira] [Commented] (CASSANDRA-15080) Paxos tables should allow a configurable chunk length
[ https://issues.apache.org/jira/browse/CASSANDRA-15080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634824#comment-17634824 ]
Aleksey Yeschenko commented on CASSANDRA-15080:
-----------------------------------------------
Actually allowing to modify these via {{ALTER}} would be unfortunately quite a bit involved. But we can load these from cassandra.yaml when defining the table as a compromise?
> Paxos tables should allow a configurable chunk length
> -----------------------------------------------------
>
> Key: CASSANDRA-15080
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15080
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Lightweight Transactions
> Reporter: Jon Haddad
> Assignee: Jon Haddad
> Priority: Normal
> Labels: performance
> Attachments: flamegraph-bad-perf.svg
>
>
> In doing some research for a client on LWTs, I found that once we start pushing a node hard enough, with enough LWTs, decompressing the data in the paxos table takes up quite a bit of time. I've attached an SVG flame graph showing about 10% of time is spent in LZ4_decompress_fast in queries hitting the paxos table.
> We should allow the user to modify the compression settings on this table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org