Merge pull request #34 from Colin-XKL/update-img-url

Update imgs' CDN URL
This commit is contained in:
2022-05-05 20:45:17 +08:00
committed by GitHub

View File

@@ -25,25 +25,25 @@ tags:
[colins-blog.netlify.app](https://colins-blog.netlify.app)
![Netlify在国内的速度检测](https://blog-1301127393.cos.ap-shanghai.myqcloud.com/BlogImgs/20220505191719.png)
![Netlify在国内的速度检测](https://blog-1301127393.file.myqcloud.com/BlogImgs/20220505191719.png)
**Vercel**
[colinx-blog.vercel.app](https://colinx-blog.vercel.app)
![Vercel在国内的速度检测](https://blog-1301127393.cos.ap-shanghai.myqcloud.com/BlogImgs/20220505191728.png)
![Vercel在国内的速度检测](https://blog-1301127393.file.myqcloud.com/BlogImgs/20220505191728.png)
**Azure**
[nice-glacier-095b09e00.1.azurestaticapps.net](https://nice-glacier-095b09e00.1.azurestaticapps.net)
![Azure在国内的速度检测](https://blog-1301127393.cos.ap-shanghai.myqcloud.com/BlogImgs/20220505191733.png)
![Azure在国内的速度检测](https://blog-1301127393.file.myqcloud.com/BlogImgs/20220505191733.png)
**CloudFlare Pages**
[colinx-blog.pages.dev](https://colinx-blog.pages.dev)
![Cloudflare Pages在国内的速度检测](https://blog-1301127393.cos.ap-shanghai.myqcloud.com/BlogImgs/20220505191738.png)
![Cloudflare Pages在国内的速度检测](https://blog-1301127393.file.myqcloud.com/BlogImgs/20220505191738.png)
emmm Cloudflare 这在国内的速度可太拉胯了,虽说可以通过自选节点的方式曲线救国,但想了想还是算了。利用好其他三家的节点应该足够国内大部分用户访问。
@@ -86,25 +86,25 @@ before
检测一波,红了好几个省份
![image-20220504222718997](https://blog-1301127393.cos.ap-shanghai.myqcloud.com/BlogImgs/20220505191745.png)
![image-20220504222718997](https://blog-1301127393.file.myqcloud.com/BlogImgs/20220505191745.png)
慢点可以接受,线路不通可不能忍。之前粗略筛的几个节点,如今过了快两年了,线路估计也发生了变化,简单跑了一下这几条,发现这个线路现在的状况实在不咋地
![trace](https://blog-1301127393.cos.ap-shanghai.myqcloud.com/BlogImgs/20220505191749.png)
![trace](https://blog-1301127393.file.myqcloud.com/BlogImgs/20220505191749.png)
这圈子兜的也太大了些。。。哦原来是 Digital Ocean 的节点啊,那没事了。
亚马逊的节点稍微好些,没有绕道日本这么离谱的行为
![trace](https://blog-1301127393.cos.ap-shanghai.myqcloud.com/BlogImgs/20220505191834.png)
![trace](https://blog-1301127393.file.myqcloud.com/BlogImgs/20220505191834.png)
再来看看 vercel 节点的表现
![trace2](https://blog-1301127393.cos.ap-shanghai.myqcloud.com/BlogImgs/20220505191933.png)
![trace2](https://blog-1301127393.file.myqcloud.com/BlogImgs/20220505191933.png)
这里是自选的节点,直连东京节点,好评
![trace3](https://blog-1301127393.cos.ap-shanghai.myqcloud.com/BlogImgs/20220505192022.png)
![trace3](https://blog-1301127393.file.myqcloud.com/BlogImgs/20220505192022.png)
但是默认的 AnyCast 节点这个路由就稍微绕路了,看来大中华区还是得自己动手调整下线路
@@ -112,7 +112,7 @@ before
after
![image-20220505190011635](https://blog-1301127393.cos.ap-shanghai.myqcloud.com/BlogImgs/20220505192417.png)
![image-20220505190011635](https://blog-1301127393.file.myqcloud.com/BlogImgs/20220505192417.png)
检测优化过程就不赘述了,都是拿几个基本的工具`ping``tcping``httping``traceroute`还有上文的全国网速检测网站对那几个节点挨个检测,直接上结论: