QUOTE(Epic_winner091 @ Sep 8 2024, 09:49 PM)
Is the throttling deliberate or is it to mitigate congestion?
QoS works like this.
I tell you got 100M speed, instead of using 100M fully and causing lag to important traffic, you sure only assign 80M for bulk down/up, 20M for important.
For better example, YouTube, if you trying to grab video from non Malaysia CDN/peer, throttle observed, but it is full speed at MY CDN/peer.
You only need to cache this 10GB of video file by grabbing it from SG, then sharing to others within Malaysia, let said it take 10M/s oversea traffic to did that, then others is just local traffic within MY.
If you give everyone going to SG CDN, then everyone in Malaysia download 10GB of video file from SG, it take >10M/s to did that, 10 ppl then 100M/s oversea traffic, and lol.
So, it gonna break if you don't throttling those people doing it, and well, result in current status.
---
The only problem is, Why TM failed to did that.
I observed that, Shopee moving CDN to MY, then back to SG, same to Lazada, and lastly the unicast of CloudFlare CDN server.(moved by TM)
Is it caused by wrong setup of DNS(as you may know, 1111 give you SG instead of MY server), or because it is too expensive to buy traffic from TM?
---
Ok, observed lazada moving back to MY already, but...
lol, even Lazada using Bytedance and zenlayer as their MY CDN, not AliYun.
Shopee still at SG, so I guess all traffic assigned for Shopee 9.9 sale and CloudFlare then.
Still, it valid, why CloudFlare and shopee traffic still going to SG, you better ask how much TM asking them to pay.

PS: It save cost only for static data like image video etc, it still need to reach back SG for computation la, but by result, traffic saved a lot.
So the best is static at local CDN, direct API traffic to compute server, unless you need prefect exp for customer, then all done by local CDN.
This post has been edited by BenYeeHua: Sep 8 2024, 10:30 PM