增加针对相关实例的EC2限制是否可以解决延迟问题? [英] Will increasing my EC2 limit for the relevant instance solve a latency issue?

查看:72
本文介绍了增加针对相关实例的EC2限制是否可以解决延迟问题?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我是菜鸟,并且在一个特定实例上遇到了问题。

I'm a noob and am having a problem with one specific instance.

有人可以告诉我增加此实例的(?)限制是否可以解决问题?

Can anyone tell me if increasing some (?) limit for this instance will solve the problem?

实例类型为t2.small。

The instance type is t2.small.

此外,客户在网站超时方面遇到了麻烦尝试注册时。我认为这会引发状态500错误,如下所述。

Also, a customer has had trouble with the website timing out when attempting to sign-up. I assume that would throw a status 500 error, as referenced below, right.

因此,这是否意味着某种限额的增加会消除注册的超时问题?

Thus, does this mean a limit increase of some sort would eliminate the timeout problem with sign up?

两个警报已经反复响起。以下是第一个的详细信息:

Two alarms have been going off repeatedly. Here's more info on the first:

警报详细信息:


  • 名称: prod-lb-latency-alarm

  • 描述:当延迟时间超过1秒时发出警报

  • Name: prod-lb-latency-alarm
  • Description: Alarm when Latency exceeds 1s

受监控的指标:


  • MetricNamespace: AWS / ELB

  • 指标名称:延迟

  • 维度: [LoadBalancerName = nameofinstance-elb]

  • 时间段: 60秒

  • 统计信息:平均

  • 单位:未指定

  • MetricNamespace: AWS/ELB
  • MetricName: Latency
  • Dimensions: [LoadBalancerName = nameofinstance-elb]
  • Period: 60 seconds
  • Statistic: Average
  • Unit: not specified

这是第二个:

警报详细信息:


  • 名称: prod-elb-elevated-error-rates
  • >
  • 说明:服务器错误率提高了(状态500错误很多)

  • 状态更改:确定->警报

  • Name: prod-elb-elevated-error-rates
  • Description: Server error rates are elevated (lots of status 500 errors)
  • State Change: OK -> ALARM

推荐答案

Amazon EC2 T2实例确实对CPU和网络带宽有限制。基本上,实例越大,您得到的就越多!

Amazon EC2 T2 instances do have limitations on CPU and Network bandwidth. Basically, the bigger the instance, the more you get!

价格差异很小,因此一定会增加实例大小一会儿并查看它是否可以解决您的问题。

The price difference is rather small, so by all means increase the instance size for a while and see whether it fixes your issues.

T2实例非常适合突发工作负载,该实例有时很忙,有时很空闲。您可以激活 T2无限 以避免CPU问题。仅在平均CPU高于实例类型的正常T2限制的情况下,费用才会更高。

T2 instances are great for bursty workloads, where the instance is sometimes busy and sometimes idle. You can activate T2 Unlimited to avoid the CPU issues. It only costs more if the average CPU is above the normal T2 limits for the instance type.

这篇关于增加针对相关实例的EC2限制是否可以解决延迟问题?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆