1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
From https://aws.amazon.com/rds/instance-types/
instance class db.t2.micro contains 1 vCPU, 6 CPU credits/hour, 1 GiB memory . Comparing the details db.t3.micro and db.t4g.micro share similar capabilities
Instance class vCPU CPU credits/hour Mem
------------- ----- ----------------- ----
db.t3.micro 2 12 1
db.t4g.micro 2 12 1
Contenus pertinents
- demandé il y a 2 ans
- demandé il y a un an
- demandé il y a un mois
AWS OFFICIELA mis à jour il y a 3 ans- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 3 ans
I have a question about this (and an interest in getting it right, I got the same email from AWS about retirement of some of my RDS instance types) - the current instance asked about here is db.t2.micro which is Intel Xeon-based under the hood.
db.t4g.micro is a target that is suggested as a good fit, this is an Arm-based Graviton2 processor under the hood.
So, if you want to go from db.t2.micro to db.t4g.micro can you just basically stop the database, change the instance class, and then start it up and it will be seamless? I just ask because with EC2 (and I know that EC2 != RDS) you can't seamlessly upgrade from an instance from t2.micro to t4g.micro.
The "Vertical scaling" section of https://aws.amazon.com/blogs/database/scaling-your-amazon-rds-instance-vertically-and-horizontally/ suggests it's straightforward, would be nice to get that confirmed.
Please consider the below step before you do the change of instance class -- https://aws.amazon.com/blogs/database/key-considerations-in-moving-to-graviton2-for-amazon-rds-and-amazon-aurora-databases/