Skip to content

Lab/cluster-bot: change default AWS IPI to instance=m6i and EBS=gp3#6

Closed
mtulio wants to merge 2 commits intomasterfrom
lab-aws-m6i-gp3
Closed

Lab/cluster-bot: change default AWS IPI to instance=m6i and EBS=gp3#6
mtulio wants to merge 2 commits intomasterfrom
lab-aws-m6i-gp3

Conversation

@mtulio
Copy link
Copy Markdown
Owner

@mtulio mtulio commented Oct 26, 2021

Changes to increase control plane performance just changing to the most recent AWS instance (m6i) and volume type (gp3). Joint PRs to be used in cluster bot.

This is WIP validation to support gp3 as default on IPI, due the benefits compared to gp2.

Overview of improvements of gp3 compared to gp2:
- The baseline IOPS was increased to 3,000 : gp2 volumes is allowed to burst up to 3,000 IOPS with a baseline of 1:3 GiB:IOPS, so volumes with low capacity will have a low baseline and can be impacted with long periods of I/O
- Now it is allowed to increase the throughput regardless of capacity with a baseline of 125 MiB/s (extra fee is charged per MiB/s provisioned above the baseline)
- Now it is allowed to increase the IOPS regardless of capacity with a baseline of 3,000 IOPS (extra fee is charged per IOPS provisioned above the baseline)
- Cheaper : The cost of gp3 is 20% lower than gp2 in a standard baseline

More details on the study case on SPLAT-253.
@mtulio mtulio changed the title Lab only: aws m6i gp3 Lab/cluster-bot: change default AWS IPI to instance=m6i and EBS=gp3 Oct 26, 2021
@mtulio mtulio closed this Nov 11, 2021
@mtulio mtulio deleted the lab-aws-m6i-gp3 branch December 15, 2021 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant