blocks|key|556495|text|是的，亚马逊有一个弹性网卡网络接口的概念。虽然您可以为实例添加NIC，但它仍然是一个逻辑接口。网络管道的供应和可用性在很大程度上取决于(完全取决于)您选择的类型实例。Amazon有几种类型/系列的实例，如R、I、C、D、G-分别在内存、IO、计算、密集存储、GPU上进行了优化。你可以看看你能不能挤到max。他们中的一员。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|556496|不管你选择哪种类型作为实例类型，你基本上都会达到一个阈值，并且不能扩展到超过某个点。与内存/+CPU等其他可伸缩性因素相比，可伸缩性尤其独特。|556497|修改您的体系结构，而不是拥有非常大的实例，而不是后面的几个中型或大型实例和ELB。|556498|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Yes Amazon has a concept of ENI - Elastic Network Interface. While you can additional NIC to the instance; it is still a logical interface. The provisioning and availability of the network pipe highly depends on (well purely depends on) the type instance you choose. Amazon has several types / family of instance like R, I, C, D, G - optimized at Memory, IO, Compute, Dense Storage, GPU respectively. You can see if you can squeeze max. out of them.

Irrespective of what ever you choose as instance type, you would essentially hit a threshold and wouldn't be able to scale beyond a certain point. Scalability particularly unique against other scalability factors like Memory / CPU.

Modify your architecture and rather than having very big / bigger instance have several of the medium or large instances behind and ELB.

blocks|key|557443|text|如果您受到带宽的限制，那么当您达到带宽限制时，该图形将变得平坦。此外，正如其他人指出的那样，只有1MB/s的速度和3MB/s的速度，我可以在t2.microto外部互联网上做更多的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|557444|系统对每个请求做了什么？下面是我要看的一系列事情，按顺序排列：|557445|557446|线程:您的应用程序中是否存在只有一个线程可以访问资源的瓶颈？这将保持较低的CPU使用率，但结果与您看到的模式完全相同。应用程序或服务器中的|unordered-list-item|557447|错误的并发模式。负载测试，并寻找它变得越来越慢，随着连接的增加，同时进行nothing.|557448|Individual中央处理器:是否有一个中央处理器负载到100%25，而其他的大部分是空闲的？(对于30%2B内核，饱和的CPU只能提供3%25的CPU使用率)。一个饱和的CPU+%2B其他空闲的CPU通常意味着并发问题，可能是在连接处理中。|557449|内存使用是什么样子的？你在使用交换吗？(如果是这样，这是一个非常糟糕的迹象，并将导致问题)。如果内存使用过多，通常是内存中的会话存储或过大的处理程序线程池有问题。|557450|磁盘I/O或外部网络请求:您是在读取还是写入每个请求？vmstat将告诉您是否花费了很长时间等待I/O得到服务。如果是这样的话，我会在做任何事情之前查看日志。|557451|+c4.8xlarge实例仅使用EBS，如果存储是磁性的，并且您写入访问日志，则每秒将获得数百次写入。一般用途的concurrent|557452|557453|每GB基数可提供3个IO/s，但可能会激增至3000个，直到IO配额耗尽为止。|557454|操作系统将尝试合并写入，但会有数千个SSD|557455|557456|​|557457|这并不是不可能的，但如果您的请求非常小，您可能会在网络层遇到连接创建或每秒数据包数的瓶颈。|557458|entityMap^0|0|0|0|0|0|0|0|1|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|16|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|G|7|19|8|@]|9|@]|A|$]]|$1|N|3|O|5|G|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|G|7|1B|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1D|8|@]|9|@]|A|$]]|$1|U|3|V|5|G|7|1E|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1H|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|12|$]]

If you were limited by bandwidth, that graph would become flat when you hit the limit. Further, as others pointed out that is only 1 MB/s out and 3 MB/s in, and I can do more than that on a t2.micro to the external internet.

What is the system doing with each request? Here are a list of things I would look at, in order:

<ul>
<li>Threading: are there bottlenecks in your application where only one thread can access a resource? That would keep CPU use low but cause exactly the pattern you saw. </li>
<li>Bad concurrency patterns in your application or server. Load test and look for it getting slower and slower as connections increase, while doing nothing.</li>
<li>Individual CPU: is one CPU loaded to 100% while others are mostly idle? (with 30+ cores, a saturated CPU would only give you 3% CPU use). One saturated CPU + others idle usually means a concurrency issue, probably in connection handling.</li>
<li>What is memory use like? Are you using swap at all? (that is a VERY bad sign if so, and would cause the issue). If memory use is excessive, often session storage in memory or excessively sized handler thread pools are at fault.</li>
<li>Disk I/O or external network requests: are you reading or writing with each request? vmstat will tell if you are spending a long time waiting for I/O to be serviced. If that is the case, I'd look at logging before anything. 

<ul>
<li>The c4.8xlarge instances use EBS only, if the storage is magnetic and you write to access logs, you get a few hundred writes per second. General purpose SSDs give you 3 IO/s per GB base, but can burst to 3000 until they run out of IO credits.</li>
<li>The OS will try to combine writes, but with thousands of concurrent</li>
</ul></li>
</ul>

It's not impossible but very unlikely that you might be bottlenecked at the network layer with connection creation or packets-per-second, if your requests are very small.

blocks|key|59523|text|你的NetworkIn和Out实际上是大于50mb/s的。如果你的CPU和内存保持在合理的范围内，那么你的实例就很好。你还应该检查你的数据库的连接日志(假设你在你的系统上运行一个RDB+)，速度变慢实际上可能是因为你的数据库响应太慢，导致web服务器响应更慢。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|59524|此外，您应该使用AWS负载均衡器运行您的系统，并在网络输入/输出上使用触发器进行设置和自动缩放。这样，就会启动一个辅助实例来帮助临时增加网络上的负载。如果根本原因确实是数据库上连接的增加，那么负载均衡器将不会帮助解决问题。相反，你想改进缓存设置，这样每个用户/网站连接的数据库负担就会更小。|59525|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Your NetworkIn and Out is actually >50mb/s. If your CPU and Memory stayed within reasonable ranges then your instance is fine. You should also check the connection log on your database (assuming you running an RDB with your system) the slow down actually could be caused from the slow response on your database that makes the web server respond slower. 

Also, you should run your system with a AWS Loadbalancer and setup and autoscaler with a trigger on the network in/out. That way a secondary instance gets launched to assist with the temporary increase in load on the network. If the root cause is indeed the increase in connection on your database, then the load balancer will not help with the problem. Instead you want to improve your cache setup so there is less burden on the database per user/connection to your website.

We hosted a site in AWS EC2 of type c4.8xlarge. It is a fairly large system with lot of memory and compute resources. Thousands of users tried to access the system during a 2 hour timeframe this weekend. While it did not crash, it slowed down quite a bit and failed to perform at the expected level. Analyzing the stats showed that limited network bandwidth is the main cause of the slowdown. The CPU usage stayed below 6%, but NetworkIn and NetworkOut seem to have peaked at 60MB and 200MB respectively during that timeframe. While I'm not an networking expect, some reading online seemed to indicate that all the traffic going through one NIC could be the main cause of limited network bandwidth. Is this true? Would hosting the site on a different type of EC2 instance help increase the network bandwidth? Here is how the networkIn and networkOut metrics looked like under heavy load.

<img src="https://i.stack.imgur.com/KmLin.png" alt="networkIn and networkOut metrics chart">

How to increase network bandwidth of AWS EC2 instance?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们在AWS EC2中托管了一个c4.8xlarge类型的站点。它是一个相当大的系统，具有大量的内存和计算资源。上周末，数千名用户试图在2小时的时间内访问该系统。虽然它没有崩溃，但它的速度慢了不少，未能达到预期的性能水平。分析统计数据显示，网络带宽有限是导致速度减慢的主要原因。CPU使用率保持在6%以下，但Networ...

问如何增加AWS EC2实例的网络带宽？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何增加AWS EC2实例的网络带宽？EN