[
https://issues.apache.org/jira/browse/CASSANDRA-18027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17675994#comment-17675994
]
Michael Semb Wever commented on CASSANDRA-18027:
------------------------------------------------
Summary to date of the thread: no vetoes to the change in trunk, there were
vetoes to 4.1.0, and there was a desire to have benchmarking heap data
presented.
It is unclear if the vetoes against 4.1.0 also apply to 4.1.1, and the extent
of benchmarking required when we know G1 is really the only option when
CASSANDRA-16895 / CASSANDRA-16501 lands. It's also worth re-iterating that
Alex's blog post does put data on the table for us, if we're happy to go with
that this time while we work on what our pre-commit performance testing for the
project is (ref: [this dev
thread|https://lists.apache.org/thread/kzbv632tm0j99mg10z24wb8f09z0r81z]).
> 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: High
> Fix For: 4.1.x, 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]
