fengyqf

iOS, 没错，就是苹果移动设备的操作系统本身，让我感受到什么叫灿若犬翔、烂出天际。前几年使用 iPad 几年还是相当正面评价荡然无存

阿里云上海、上海电信企业宽带，200ms 上下，这延迟完全没优势吧


[阿里云上海]
[root@iZufxxx ~]# ping -c 10 43.134.59.36
PING 43.134.59.36 (43.134.59.36) 56(84) bytes of data.
64 bytes from 43.134.59.36: icmp_seq=1 ttl=40 time=210 ms
64 bytes from 43.134.59.36: icmp_seq=2 ttl=40 time=209 ms
64 bytes from 43.134.59.36: icmp_seq=3 ttl=40 time=209 ms
64 bytes from 43.134.59.36: icmp_seq=4 ttl=40 time=209 ms
64 bytes from 43.134.59.36: icmp_seq=5 ttl=40 time=209 ms
64 bytes from 43.134.59.36: icmp_seq=6 ttl=40 time=209 ms
64 bytes from 43.134.59.36: icmp_seq=7 ttl=40 time=209 ms
64 bytes from 43.134.59.36: icmp_seq=8 ttl=40 time=209 ms
64 bytes from 43.134.59.36: icmp_seq=9 ttl=40 time=209 ms
64 bytes from 43.134.59.36: icmp_seq=10 ttl=40 time=209 ms

--- 43.134.59.36 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 209.378/209.445/209.581/0.057 ms
[root@iZufxxx ~]#


[上海电信企业宽带]
C:\Users\zzz>ping -n 10 43.134.59.36

正在 Ping 43.134.59.36 具有 32 字节的数据:
来自 43.134.59.36 的回复: 字节=32 时间=189ms TTL=48
来自 43.134.59.36 的回复: 字节=32 时间=191ms TTL=48
来自 43.134.59.36 的回复: 字节=32 时间=188ms TTL=48
来自 43.134.59.36 的回复: 字节=32 时间=191ms TTL=48
来自 43.134.59.36 的回复: 字节=32 时间=188ms TTL=48
来自 43.134.59.36 的回复: 字节=32 时间=189ms TTL=48
来自 43.134.59.36 的回复: 字节=32 时间=188ms TTL=48
来自 43.134.59.36 的回复: 字节=32 时间=188ms TTL=48
来自 43.134.59.36 的回复: 字节=32 时间=188ms TTL=48
来自 43.134.59.36 的回复: 字节=32 时间=191ms TTL=48

43.134.59.36 的 Ping 统计信息:
数据包: 已发送 = 10 ，已接收 = 10 ，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 188ms ，最长 = 191ms ，平均 = 189ms


[AWS 东京]
# ping -c 10 43.134.59.36
PING 43.134.59.36 (43.134.59.36) 56(84) bytes of data.
64 bytes from 43.134.59.36: icmp_seq=1 ttl=52 time=67.8 ms
64 bytes from 43.134.59.36: icmp_seq=2 ttl=52 time=67.8 ms
64 bytes from 43.134.59.36: icmp_seq=3 ttl=52 time=68.0 ms
64 bytes from 43.134.59.36: icmp_seq=4 ttl=52 time=67.9 ms
64 bytes from 43.134.59.36: icmp_seq=5 ttl=52 time=67.9 ms
64 bytes from 43.134.59.36: icmp_seq=6 ttl=52 time=67.9 ms
64 bytes from 43.134.59.36: icmp_seq=7 ttl=52 time=67.9 ms
64 bytes from 43.134.59.36: icmp_seq=8 ttl=52 time=67.8 ms
64 bytes from 43.134.59.36: icmp_seq=9 ttl=52 time=67.9 ms
64 bytes from 43.134.59.36: icmp_seq=10 ttl=52 time=67.9 ms

--- 43.134.59.36 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 67.879/67.921/68.021/0.287 ms


[bw 洛杉矶]
$ ping -c 10 43.134.59.36
PING 43.134.59.36 (43.134.59.36) 56(84) bytes of data.
64 bytes from 43.134.59.36: icmp_seq=1 ttl=51 time=172 ms
64 bytes from 43.134.59.36: icmp_seq=2 ttl=51 time=172 ms
64 bytes from 43.134.59.36: icmp_seq=3 ttl=51 time=172 ms
64 bytes from 43.134.59.36: icmp_seq=4 ttl=51 time=172 ms
64 bytes from 43.134.59.36: icmp_seq=5 ttl=51 time=172 ms
64 bytes from 43.134.59.36: icmp_seq=6 ttl=51 time=172 ms
64 bytes from 43.134.59.36: icmp_seq=7 ttl=51 time=172 ms
64 bytes from 43.134.59.36: icmp_seq=8 ttl=51 time=172 ms
64 bytes from 43.134.59.36: icmp_seq=9 ttl=51 time=172 ms
64 bytes from 43.134.59.36: icmp_seq=10 ttl=51 time=172 ms

--- 43.134.59.36 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 172.288/172.333/172.386/0.264 ms

难用，是跟谁比，该不是 iOS 吧，那个难用到死的系统，祖传 bug 、脑残的设定，还宁死不改。

数据库通常不会比 csv 小，除了数据还要存索引，都要空间；字符串型字段，如果固定长度的表，还会大量浪费空间。

最好备份重要文件，重装系统，迁移回数据。跨大版本很容易出问题。如果不怕死的话，甚至可以直接把 /home, /var 等下面重要文件直接复制粘贴回去，再确认你的软件是不是正常工作，正常就可以假装升级成功。

楼主不觉得头像带数字是对“强迫症患者”最大的不尊重吗..

phpMyAdmin，大文件导入才试用 navi

@leafleave 感谢*65535

最新：还剩一个 WordPress 客户端，其他都好了，包括 Google 家的 chrome, 照片