- 最新
- 投票最多
- 评论最多
Lightsail is very unreliable, I'm running two identical lightweight servers on LightSail and EC2, every few months the LightSail server will suddenly slow to a crawl that my website times out. I check the CPU utilization and it's under 1%, the disk usage is extremely low, credits are at a 100%. There's something wrong with the LightSail infrastructure, either some other VM from another user is taking up all the resources and starting the other VM's sharing the hardware or their setup is buggy. The only solution I've found to this is to stop and restart the instance and then it becomes a 100% responsive instantly. My guess is after a stop/start it spins it up on a different underlying hardware. I've never had an issue with the EC2 instance but the Lightsail instance (all of them) like clockwork will slow to a crawl and eventually fail (yup, the alarms go off because it stop responding to Amazon's own monitoring system) and I have to stop/start them again to fix it (or if I leave it for a 12+ hours or a few days, it'll eventually come back online but that's not a solution). Something is VERY VERY broken about Lightsail and Amazon refuses to acknowledge or fix it. I've been reporting this for about 3 years now.
One place to start is health metrics, which you can read about here: https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-viewing-instance-burst-capacity#identifying-instance-burst
Another thing to consider is whether you're exhausting your instance's burst capacity: https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-viewing-instance-health-metrics. If so, you may want to upgrade to a more powerful instance type to ensure adequate performance for your workload.
相关内容
- AWS 官方已更新 3 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前
I'm also facing the same issue on gigglewave.com the database server is extremely slow that uploading 70MB database file takes forever and i'm getting totaly frustrated. Any help will be highly appreciated to fix this. I'm only running 1 blog on 1 GB instance.