[
https://issues.apache.org/jira/browse/CASSANDRA-18027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17632711#comment-17632711
]
Michael Semb Wever commented on CASSANDRA-18027:
------------------------------------------------
bq. Curious - were those in-memory max throughput, or fixed velocity latency,
or spilling over to disk dealing with large workloads?
>From production metrics, to various benchmarks with fixed throughput and
>disk/compaction activity.
bq. I'm just noodling on how we benchmark things as a project historically and
whether there'd be value in clarifying when and how we benchmark different
things;
Completely agree. I'm hoping we create a better empirical and data-based
precedent moving forward, e.g. when introducing ZGC and Shenandoah defaults.
Hoping we can skip due diligence on this ticket because the data is "in the
past" already.
> Use G1GC as default
> -------------------
>
> Key: CASSANDRA-18027
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18027
> Project: Cassandra
> Issue Type: Task
> Components: Local/Config
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 4.x
>
>
> G1GC is well battle tested now, and the recommended configuration for most
> users. CMS can work well on smaller heaps but requires more tuning, initially
> and over time. G1GC just works. CMS was deprecated in JDK 9.
> Patch at
> https://github.com/apache/cassandra/compare/trunk...thelastpickle:cassandra:mck/7486/trunk
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
