问题描述
我不清楚 EBS 与实例存储对我在 Amazon EC2 上的实例有何好处.如果有的话，EBS 似乎更有用(停止、启动、持续 + 更快的速度)，而成本差异相对较小......?此外，考虑到 EBS 仍然相对较新，现在是否有更多人使用 EBS 的指标?
I'm unclear as to what benefits I get from EBS vs. instance-store for my instances on Amazon EC2. If anything, it seems that EBS is way more useful (stop, start, persist + better speed) at relatively little difference in cost...? Also, is there any metric as to whether more people are using EBS now that it's available, considering it is still relatively new?
推荐答案
最重要的是你应该几乎总是使用 EBS 支持的实例.
The bottom line is you should almost always use EBS backed instances.
原因
- 可以设置 EBS 支持的实例，使其不会(意外)通过 API 终止.
- EBS 支持的实例可以在您不使用它们时停止，并在您再次需要它们时恢复(例如暂停虚拟 PC)，至少我的使用模式比我花在几十 GB 的实例上节省了更多的钱EBS 存储.
- EBS 支持的实例在崩溃时不会丢失其实例存储(不是所有用户都需要，但可以加快恢复速度)
- 您可以动态调整 EBS 实例存储的大小.
- 您可以将 EBS 实例存储转移到一个全新的实例(如果您在 Amazon 上运行的硬件变得易碎或死机，这种情况不时发生，则很有用)
- 启动 EBS 支持的实例更快，因为不必从 S3 获取图像.
- 如果您的 EBS 支持的实例的硬件是 安排维护，停止和启动实例会自动迁移到新硬件.我还能够通过强制停止实例并再次启动它来在故障硬件上移动 EBS 支持的实例(您的里程可能因故障硬件而异).
- EBS backed instances can be set so that they cannot be (accidentally) terminated through the API.
- EBS backed instances can be stopped when you're not using them and resumed when you need them again (like pausing a Virtual PC), at least with my usage patterns saving much more money than I spend on a few dozen GB of EBS storage.
- EBS backed instances don't lose their instance storage when they crash (not a requirement for all users, but makes recovery much faster)
- You can dynamically resize EBS instance storage.
- You can transfer the EBS instance storage to a brand new instance (useful if the hardware at Amazon you were running on gets flaky or dies, which does happen from time to time)
- It is faster to launch an EBS backed instance because the image does not have to be fetched from S3.
- If the hardware your EBS-backed instance is scheduled for maintenance, stopping and starting the instance automatically migrates to new hardware. I was also able to move an EBS-backed instance on failed hardware by force-stopping the instance and launching it again (your mileage may vary on failed hardware).
我是 Amazon 的重度用户，一旦该技术推出测试版，我就将我的所有实例切换到 EBS 支持的存储.我对结果非常满意.
I'm a heavy user of Amazon and switched all of my instances to EBS backed storage as soon as the technology came out of beta. I've been very happy with the result.
EBS 仍然可能失败 - 不是灵丹妙药
请记住，任何基于云的基础架构都可能随时出现故障.相应地规划您的基础设施.虽然与临时存储实例相比，EBS 支持的实例提供了一定程度的持久性，但它们可能并且确实会失败.拥有一个 AMI，您可以从中根据需要在任何可用区启动新实例，备份重要数据(例如数据库)，如果预算允许，运行多个服务器实例以实现负载平衡和冗余(最好在多个可用区中)).
Keep in mind that any piece of cloud-based infrastructure can fail at any time. Plan your infrastructure accordingly. While EBS-backed instances provide certain level of durability compared to ephemeral storage instances, they can and do fail. Have an AMI from which you can launch new instances as needed in any availability zone, back up your important data (e.g. databases), and if your budget allows it, run multiple instances of servers for load balancing and redundancy (ideally in multiple availability zones).
什么时候不要
在某些时间点，在实例存储实例上实现更快的 IO 可能更便宜.曾经有一段时间，它肯定是真的.现在有多种 EBS 存储选项，可满足多种需求.选项及其定价随着技术的变化而不断变化.如果您有大量真正一次性的实例(如果它们消失，它们不会对您的业务产生太大影响)，请计算成本与性能.EBS 支持的实例也可能随时消亡，但我的实践经验是 EBS 更持久.
At some points in time, it may be cheaper to achieve faster IO on Instance Store instances. There was a time when it was certainly true. Now there are many options for EBS storage, catering to many needs. The options and their pricing evolve constantly as technology changes. If you have a significant amount of instances that are truly disposable (they don't affect your business much if they just go away), do the math on cost vs. performance. EBS-backed instances can also die at any point in time, but my practical experience is that EBS is more durable.
这篇关于EBS 与实例存储的优势(反之亦然)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！