You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Bottlerocket images default to creating two volumes (as explained in the README), and the AWS AMIs have these volumes set as gp2 by default. For example, ami-0b2c067c54702aea4.
I suggest setting it to gp3 instead, since it provides lower price per GB, and the new Amazon Linux version (AL2023) already sets it as default.
I understand the volume type may be overridable, depending on one's deployment scenario, but I don't see any obvious upside to maintaining gp2 as the default, so I decided to leave this suggestion here.
The text was updated successfully, but these errors were encountered:
Hi @jfrancisco0, thanks for bringing this up. It is a very valid suggestion to make the default volume type to gp3. We have made some evaluation on gp3 in the past. While gp3 obviously provides a more cost effective way to achieve the SSD performance with better baseline performance, we did notice that the boot time with gp3 is slightly slower than with gp2.
However, it has been a while since the last time we perform that evaluation. I will work with the team to run another boot time tests and see if we see better result.
Again, thanks for bringing this to our attention, I will keep you posted with my testing.
What I'd like:
Currently, Bottlerocket images default to creating two volumes (as explained in the README), and the AWS AMIs have these volumes set as
gp2
by default. For example,ami-0b2c067c54702aea4
.I suggest setting it to
gp3
instead, since it provides lower price per GB, and the new Amazon Linux version (AL2023) already sets it as default.I understand the volume type may be overridable, depending on one's deployment scenario, but I don't see any obvious upside to maintaining
gp2
as the default, so I decided to leave this suggestion here.The text was updated successfully, but these errors were encountered: