高性能高可用跟踪系统
我目前拥有一项跟踪服务，记录各种来源的访问。有时，我们会记录访问情况并重定向给我们的客户，或者让客户致电我们报告访问情况。该架构是配置在负载均衡器后面的两个工作框。该系统使用 Amazon EC2 设置，使用的负载均衡器是 Amazon 的 Elastic LB。
我做了一些基准测试并注意到明显的网络延迟。通过负载均衡器的流量所遭受的延迟至少是直接到达任何盒子的两倍。
- 有没有人遇到过这样的问题并尝试解决它？这是 Amazon EC2 特定问题吗？
- 是否有任何其他正在使用的架构可以显着降低我的网络延迟。例如，使用HA使得流量不需要通过负载平衡器而是直接到达端点服务器？在我开始投入时间之前，我想听听其他人的看法。
非常感谢您抽出时间， 桑托什
I currently hold a tracking service that records visits from various sources. At times we record the visits and redirect to our clients or we let clients call us to report visits. The architecture is two worker boxes configured behind a load-balancer. This system is setup using Amazon EC2 and the load-balancer used is Amazon's Elastic LB.
I did some benchmarking tests and have noticed significant network latencies. The traffic through load-balancer suffers atleast 2 times more delay than hitting any of the boxes directly.
- Has anyone experienced such an issue and has attempted to solve it? Is this an Amazon EC2 specific issue?
- Is there any other architecture in use that would lower my network latencies significantly. e.g. Using a HA such that traffic needn't go through a load-balancer but instead hits the end point servers directly? Before I start investing time on that I wanted to hear what others think of the same.
Thanks alot for your time,
Santosh
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
改变你的LB并再试一次。 HAProxy 是一款出色的会话/cookie 感知 L7 平衡器，并且可以在 Amazon 云中进行设置。请参阅：http://agiletesting.blogspot .com/2009/02/load-balancing-in-amazon-ec2-with.html
Change your LB and give it another try. HAProxy is great session/cookie aware L7 balancer and can be setup in Amazon cloud AFAIK. See this: http://agiletesting.blogspot.com/2009/02/load-balancing-in-amazon-ec2-with.html
您必须考虑到 ELB 在一段时间后会比最初表现得更好。不要问我为什么，但事情就是这样——负载均衡器变暖？
它还实际上取决于您向 ELB 发送了多少流量。请记住，配置 ELB 的硬件看起来像是一个常规的小型实例。因此吞吐量上限为 ~25 MBit（我上次检查时）。如果您需要更多，请专注。
最后，我也建议您在专用实例上查看 Haproxy。我预计会有一些延迟，两倍的延迟听起来不真实。也许使用另一个小型实例并直接针对 ELB 进行基准测试，然后尝试
c1.medium。You have to take into account that ELBs perform better after a while, then initially. Don't ask me why, but that's how it is -- loadbalancer warming?
It also really depends how much traffic you sent the ELB. Keep in mind that the hardware the ELB is provisioned on seems like a regular small instance. So the throughput is capped at ~25 MBit (last time I checked). If you require more, go dedicated.
In the end, I too would suggest that you look Haproxy on a dedicated instance. I'd expect some delay, 2x more delay sounds unreal. Maybe use another small instance and benchmark it directly against the ELB and then try a
c1.medium.