If the problem of high peering intranet latency is solved

0

I set up peering in Singapore region to connect two vpc of the same AZ, the ping latency between EC2 of the same vpc is 100ms, but after pinging through peering the ping latency becomes 700ms.i need to reduce the latency of the network between peering

已提問 10 個月前檢視次數 424 次
2 個答案
1
已接受的答案

Hi, those latency figures are very very high, so I think something else is going on - it's not the VPC and peering infrastructure. To give you an idea, latency across the whole of Australia, from Perth to the AWS Sydney region, is well under 100ms.

Also note that a VPC is not associated with an AZ. The subnets inside are individually associated with AZs.

Also if you're peering VPCs across accounts, the AZs don't necessarily line up by name. What I mean is that AZ "a" in one account won't necessarily be the same physical AZ as "a" in another account unless you've explicitly aligned them.

專家
已回答 10 個月前
profile pictureAWS
專家
已審閱 10 個月前
1

I would expect the latency to be higher for cross-AZ traffic as compared to intra-AZ traffic because availability zones are separate from each to avoid common points of failure.

However, 100ms within the same AZ is extremely high; and 700ms (close to one second) between AZs is not normal. You should see single-digit millisecond latency between availability zones; I just tested this in the Singapore region between all three availability zones and that's what I'm seeing.

profile pictureAWS
專家
已回答 10 個月前
profile pictureAWS
專家
已審閱 10 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南