将 EC2 负载均衡与现有 WordPress 博客结合使用
我目前通过 Media Temple 有一个虚拟专用服务器，用于运行几个高流量的 Wordpress 博客。两者都容易受到突然的 StumbleUpon 流量激增（我假设）导致服务器 CPU 100% 运行并减慢一切速度。我目前对大多数静态文件使用 WP-Super-Cache、S3 和 CloudFront，但高流量仍然导致 CPU 速度变慢。
从我读到的内容来看，当流量高峰发生时，我似乎可能想使用 EC2 来帮助现有服务器。由于我目前在 Media Temple 上使用顶级虚拟专用服务器，因此我希望尽可能避免跳转到专用服务器。我感觉 AWS 可能有助于增强现有服务器的能力。我该怎么做呢？
如果我错误地使用了这些术语，我深表歉意——在服务器管理方面，我相对业余。如果这不是提高性能的最佳方法，那么建议的操作方案是什么？
I currently have a virtual dedicated server through Media Temple that I use to run several high traffic Wordpress blogs. Both tend to receive sudden StumbleUpon traffic surges that (I'm assuming) cause the server CPU to run at 100% and slow down everything. I'm currently using WP-Super-Cache, S3, and CloudFront for most static files, but high traffic is still causing slowdown on the CPU.
From what I'm reading, it seems like I might want to use EC2 to help the existing server when traffic spikes occur. Since I'm currently using the top tier of virtual dedicated servers on Media Temple, I'd like to avoid jumping to a dedicated server if possible. I get the sense that AWS might help boost the existing server's power. How would I go about doing this?
I apologize if I'm using any of these terms incorrectly -- I'm relatively amateur when it comes to server administration. If this isn't the best way to improve performance, what is the recommended course of action?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我要做的第一件事是将您的数据库服务器移动到另一个 Media Temple VPS。之后，查看哪一个 CPU 利用率达到 100%。如果是 Web 服务器，您可以创建第二个实例，并使用代理来平衡负载。如果是数据库，您也许可以创建一些索引。
或者，在 Web 服务器前面设置 Squid 缓存服务器可以减轻匿名用户的大量负载。这是维基百科采用的方法，因为页面不需要为每个用户重新呈现。
无论哪种情况，都没有一种简单的方法可以在 EC2 上增加额外容量，除非您的站点一开始就位于 EC2 上。
The first thing I would do is move your database server to another Media Temple VPS. After that, look to see which one is hitting 100% CPU. If it's the web server, you can create a second instance, and use a proxy to balance the load. If it's the database, you may be able to create some indexes.
Alternatively, setting up a Squid caching server in front of your web server can take off a lot of load from anonymous users. This is the approach Wikipedia takes, as the page doesn't need to be re-rendered for each user.
In either case, there isn't an easy way to spin up extra capacity on the EC2 unless your site is on the EC2 to begin with.
您只能拥有 3 种类型的实例。除此之外，他们不能给你任何更多的“服务器能力”。您将需要进行一些负载平衡。有软件负载均衡器，比如HAProxy、NginX，这些都不错，如果你不想处理这个，你可以在不同机器上设置高负载博客后进行DNS Round Robin。
您应该能够扩展它们，这就是 AWS 的美妙之处：扩展。
There is just 3 type of instance you can have. Other than that they cant give you any more "server power". You will need to do some load balancing. There are software Load Balancers, such as HAProxy, NginX, which are not bad, if you dont want to deal with that, you can do DNS Round Robin, after setting up the high load blogs on different machines.
You should be able to scale them, that s the beauty of AWS, scaling.