先折腾到这吧

又更换了BLOG服务器，不知道是不是咱特别喜欢折腾- -. 可惜namecheap的shared hosting 的ssh是不能当VPN用的，怨念… 这个服务器的ping值感觉不是太好。

C:\>ipconfig/flushdns && ping soulteary.com

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

Pinging soulteary.com [199.188.206.108] with 32 bytes of data:

Reply from 199.188.206.108: bytes=32 time=433ms TTL=50
Reply from 199.188.206.108: bytes=32 time=513ms TTL=50
Reply from 199.188.206.108: bytes=32 time=498ms TTL=50
Reply from 199.188.206.108: bytes=32 time=391ms TTL=50

Ping statistics for 199.188.206.108:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 391ms, Maximum = 513ms, Average = 458ms

C:\>

可以看到比之前的PING值高了一倍

C:\>ping 106.187.53.22

Pinging 106.187.53.22 with 32 bytes of data:

Reply from 106.187.53.22: bytes=32 time=269ms TTL=52
Reply from 106.187.53.22: bytes=32 time=253ms TTL=52
Reply from 106.187.53.22: bytes=32 time=262ms TTL=52
Reply from 106.187.53.22: bytes=32 time=445ms TTL=52

Ping statistics for 106.187.53.22:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 253ms, Maximum = 445ms, Average = 307ms

C:\>

C:\>ping 74.82.168.181

Pinging 74.82.168.181 with 32 bytes of data:

Reply from 74.82.168.181: bytes=32 time=271ms TTL=47
Reply from 74.82.168.181: bytes=32 time=263ms TTL=47
Reply from 74.82.168.181: bytes=32 time=258ms TTL=47
Reply from 74.82.168.181: bytes=32 time=258ms TTL=47

Ping statistics for 74.82.168.181:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 258ms, Maximum = 271ms, Average = 262ms

C:\>

甚至不如小张的某米国机房的PING值,不过资源基本没限制,而且可以设置php.ini,这些就不追求了..