- Newest
- Most votes
- Most comments
Hi David,
It appears you may have Lightsail instances created over a span of time specifically before June 29, 2023 and after. Lightsail updated the instance plans aka bundles then and consequently the older bundles provide a different CPU baseline as compared to the newer ones.
For the 32GB RAM, 8vCPU plans, baseline on older is about 17% per vCPU while that on newer is 40% - this is why the metrics view you see on Lightsail console is showing the different baseline values. Please do note that these performance baselines are per vCPU.
The document you referred does note the bundle difference in the context of some other CPU-behavior but is missing the above baseline difference. Thank you for bringing this to our notice.
If you would like to avail the newer bundles, please consider switching your older instance to the newer plans by means of creating instance-snapshots [doc1] of your current instances and creating new instances from these snapshots [doc2] using the Lightsail console.
Thanks.
Hello.
What metrics are you looking at specifically?
I created a Windows Server 2019 Lightsail instance with the same specs as yours.
My console only shows one CPU metric with baseline throughput as shown below.
Maybe your other Lightsail instances are running with lower specs like "2 vCPUs, 4 GB memory, 80 GB storage" instead of "32 GB RAM, 8 vCPUs, 640 GB SSD"?
Make sure your Lightsail specs are running with "32 GB RAM, 8 vCPUs, 640 GB SSD".
Thank you for confirmation. In my environment, everything is 40%, so I think there may be a UI bug. I recommend that you open a case with AWS Support under "Account and billing" and have an inquiry. Inquiries under "Account and billing" can be made free of charge. https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
Relevant content
- Accepted Answerasked 2 years ago
- asked 3 years ago
- asked 2 years ago
AWS OFFICIALUpdated 8 months ago- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
I created the new instance with a backup snapshot, not a (Sysprep) to do the switching. The new Instance Sustainable zone is the correct one for the new bundles, and by doing it with the backup snapshot I keep RDS CALs and other licenses without doing reactivations.
Thanks again for your answer.
Glad it helped :)