You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Kevin Gallardo (Jira)" <ji...@apache.org> on 2020/04/10 15:16:00 UTC
[jira] [Updated] (CASSANDRA-15712) Introduce MIDRES config in
CircleCI
[ https://issues.apache.org/jira/browse/CASSANDRA-15712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Gallardo updated CASSANDRA-15712:
---------------------------------------
Workflow: Cassandra Default Workflow (was: Cassandra Bug Workflow)
Issue Type: Improvement (was: Bug)
> Introduce MIDRES config in CircleCI
> -----------------------------------
>
> Key: CASSANDRA-15712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15712
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest, Test/unit
> Reporter: Kevin Gallardo
> Priority: Normal
>
> From document: [https://gist.github.com/newkek/bb79dccbe7d2f5e41b2a3daac3858fde]
> We have identified that the current HIGHRES configuration seems to require resources that might not bring the best cost efficiency to the build.
> We have also identified several "good compromise" configurations that allow to get decent performance out of the test suites, without going all out on the big config.
> It seems it would be useful for a lot of people to have this available as a {{config.yml.MIDRES}} configuration in the {{.circleci}} folder. This way we do not need to argue on modifying the {{HIGHRES}} configuration so as to not impact the people already using it , but can still have easy access the "compromise" config.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org