blocks|key|1914322|text|您的RDS和EC2实例不仅要位于同一地域，还要位于同一可用区，以最大限度地减少延迟，这一点很重要。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1914323|我在爱尔兰的EC2上托管了一个应用程序接口，并将数据库移动到我们为另一个项目设置的位于美国弗吉尼亚州的MySQL集群中，每次SQL查询的往返过程使该应用程序接口无法使用。|1914324|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|$]]

It is important to have your RDS and EC2 instances not just in the same region but also in the same availability zone to minimize the latency.

I had an API hosted in Ireland on EC2 and moved the Database to a MySQL cluster in Virginia USA that we had set up for another project and the round trip on every SQL query made the API unusable.

blocks|key|1700975|text|对我来说，这与MySQL无关，而与我在t2.medium上的实例类型有关。问题是我用完了CPU积分，因为DB上的负载太高了，余额一直在下降，直到最后，我每小时得到的积分远远少于所需的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1700976|下面是我在RDS+CloudWatch中看到的CPU+Credit+Usage：|1700977|​|1700978|📷|atomic|1700979|1700980|如果您有相同的问题，可能是时候切换到不同的实例了。实例类型列表如下：|1700981|https://aws.amazon.com/rds/instance-types/|1700982|希望这能有所帮助。|1700983|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/e24084a405235e4fd4f18deedc983fe8.png|imageAlt|1|LINK|MUTABLE|url^0|J|9|0|0|0|0|1|0|0|0|0|0|16|1|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1A|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1B|8|@]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|M|3|I|5|6|7|1F|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1G|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1H|8|@]|D|@$9|1I|A|1J|1|1K]]|E|$]]|$1|R|3|S|5|6|7|1L|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|U|$V|$5|W|X|Y|E|$Z|10|11|-4]]|12|$5|13|X|14|E|$15|Q]]]]

For me, it was nothing to do with MySQL but rather the instance type I was on <code>t2.medium</code>. The problem is I ran out of CPU credits because the load on the DB was too high and the balance kept going down until finally, I was getting far fewer credits hourly than were needed.

Here is what I saw in RDS CloudWatch under CPU Credit Usage:

<a href="https://i.stack.imgur.com/yyg1M.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/yyg1M.png" alt="enter image description here"></a>

If you have the same problem it may be time to switch to a different instance. Here is the list of instance types:

<a href="https://aws.amazon.com/rds/instance-types/" rel="nofollow noreferrer">https://aws.amazon.com/rds/instance-types/</a>

Hope this helps.

blocks|key|1914507|text|始终应在同一AWS可用区中部署源和rds，以降低网络延迟，并应在VPC中为RDS创建私有端点链路，以通过内部网络连接RDS端点，而不是通过互联网路由。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1914508|参考：https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/vpc-interface-endpoints.html|offset|length|1914509|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/vpc-interface-endpoints.html^0|0|3|2B|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Always should deploy source and rds in the same AWS availability zone for lower network latency and Should create a private endpoint link in VPC for RDS to connect RDS endpoint through the internal network instead of routing through the internet.
Reference: <a href="https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/vpc-interface-endpoints.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/vpc-interface-endpoints.html</a>

blocks|key|1914515|text|我发现在迁移到RDS之后，我所有的数据库索引都消失了！它们没有随模式和数据一起迁移。确保你的索引在那里。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1914516|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I found that after migrating to RDS all my database Indexes are gone! They weren't migrated along with the schema and data. Make sure you're indexes are there.

I have published my website on Amazon EC2 (Singapore region) and I have used MySQL RDS instance for the data storage. Everything is working very fine except performance.

I seems that, my all queries, especially the select statement, is performing very slowly. If I check this issue on my local PC, there it is working very well. But when I am trying to get data from RDS instance, it is very slow. Some of the select statements takes 2-3 seconds to fetch data.

I have properly tuned up all table indexes, and normalized/de-normalized as required. I have made all necessary settings on RDS custom parameter group (eg. max_connection, buffer etc). I don't know if I am missing something, but it didn't work for me - performance didn't increase.

So, can someone please help me with this issue?

Amazon RDS MySQL instance performs very slow

数据存储

网络延迟

数据库

路由

MySQL

我已经在亚马逊EC2 (新加坡地区)上发布了我的网站，并使用MySQL RDS实例进行数据存储。除了性能之外，一切都运行得很好。我的所有查询，特别是select语句，执行起来都很慢。如果我在我的本地PC上检查这个问题，它在那里工作得很好。但是当我尝试从RDS实例中获取数据时，速度非常慢。有些select语句需要2-3秒...

问Amazon RDS MySQL实例执行速度非常慢
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Amazon RDS MySQL实例执行速度非常慢EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Amazon RDS MySQL实例执行速度非常慢
EN