Percona Server for MongoDB is a highly scalable, zero-maintenance downtime database supporting the MongoDB
v3.0 protocol and drivers. It extends MongoDB with RocksDB and PerconaFT storage engines, as well as features like
external authentication and audit logging. Percona Server for MongoDB requires no changes to MongoDB applications
or code. The main benefits of Percona Server for MongoDB are:

• Improved single-threaded and multi-threaded performance
• Compression
• Fully ACID and MVCC transaction support
• No maintenance or scheduled downtime necessary
• Clustering key support for query acceleration
• Better read scaling and reduced lag on replica sets
• Low-impact migrations and accelerated range queries with clustering shard keys
• Fast, read-free updates
• Hot Backup
• Point-in-time Recovery
• Audit Logging
• Reduced SSD wear
• Geospatial Indexes
• Includes all MongoDB v3.0 functionality except Text Search

感觉有黑科技成分：）

Robomongo 不支持 3.x ，我已经捐助$5 给作者喝咖啡了，都半年过去了没 github commit = 0 估计项目死掉了。

https://github.com/paralect/robomongo/issues/954

再给一些有用的路由信息：

北京电信
------------------------------
traceroute to 我家水表, 30 hops max, 40 byte packets
1 119.254.162.129 (119.254.162.129) 3.357 ms 3.266 ms 3.229 ms
2 119.253.9.81 (119.253.9.81) 3.198 ms 3.169 ms 3.139 ms
3 119.253.9.49 (119.253.9.49) 0.262 ms 0.234 ms 0.204 ms
4 119.253.5.49 (119.253.5.49) 0.879 ms 0.859 ms 0.830 ms
5 119.253.4.49 (119.253.4.49) 0.801 ms 0.772 ms 2.821 ms
6 119.253.0.66 (119.253.0.66) 2.767 ms 2.734 ms 2.704 ms
7 181.5.142.219.broad.bj.bj.dynamic.163data.com.cn (219.142.5.181) 7.485 ms 7.018 ms 7.181 ms
8 * * *
9 bj141-142-118.bjtelecom.net (219.141.142.118) 1.223 ms bj141-142-122.bjtelecom.net (219.141.142.122) 2.245 ms 2.192 ms
10 202.97.53.166 (202.97.53.166) 6.566 ms 202.97.53.98 (202.97.53.98) 20.904 ms 202.97.53.86 (202.97.53.86) 16.893 ms
11 202.97.53.66 (202.97.53.66) 9.020 ms 8.991 ms 8.962 ms
12 202.97.52.182 (202.97.52.182) 175.363 ms 179.032 ms 170.797 ms
13 202.97.50.74 (202.97.50.74) 172.531 ms 202.97.50.54 (202.97.50.54) 189.027 ms 202.97.50.74 (202.97.50.74) 170.590 ms
14 xe-0-2-0-25.r01.snjsca04.us.bb.gin.ntt.net (129.250.66.25) 194.517 ms 210.258 ms 196.064 ms <--- [美国]
15 ae-10.r23.snjsca04.us.bb.gin.ntt.net (129.250.3.174) 180.196 ms 169.739 ms ae-1.r22.snjsca04.us.bb.gin.ntt.net (129.250.3.26) 186.622 ms
16 ae-4.r20.tokyjp05.jp.bb.gin.ntt.net (129.250.3.7) 249.305 ms ae-4.r21.tokyjp05.jp.bb.gin.ntt.net (129.250.2.19) 200.579 ms 260.862 ms <--- [日本]
17 ae-4.r31.tokyjp05.jp.bb.gin.ntt.net (129.250.7.76) 246.747 ms ae-3.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.7.70) 278.731 ms ae-4.r31.tokyjp05.jp.bb.gin.ntt.net (129.250.7.76) 173.541 ms
18 ae-5.r02.tokyjp03.jp.bb.gin.ntt.net (129.250.3.251) 182.511 ms 178.964 ms 179.326 ms
19 xe-0-3-0-9.r02.tokyjp03.jp.ce.gin.ntt.net (117.103.177.34) 213.540 ms 214.399 ms 221.439 ms
20 45.63.125.92.vultr.com (45.63.125.92) 176.148 ms 201.802 ms 183.309 ms
21 我家水表

北京移动
------------------------------
traceroute to 我家水表, 30 hops max, 60 byte packets
1 111.13.65.1 (111.13.65.1) 1.264 ms 1.296 ms 1.335 ms
2 111.13.61.5 (111.13.61.5) 2.963 ms 111.13.61.1 (111.13.61.1) 1.970 ms 111.13.61.5 (111.13.61.5) 3.252 ms
3 111.13.59.37 (111.13.59.37) 2.564 ms 111.13.59.41 (111.13.59.41) 0.237 ms 0.243 ms
4 111.13.0.189 (111.13.0.189) 1.552 ms 111.13.0.193 (111.13.0.193) 2.409 ms 2.473 ms
5 221.183.19.53 (221.183.19.53) 1.104 ms 1.108 ms 1.279 ms
6 221.176.15.210 (221.176.15.210) 32.989 ms 33.424 ms 44.711 ms
7 221.176.24.10 (221.176.24.10) 33.934 ms 33.445 ms 33.806 ms
8 221.176.24.138 (221.176.24.138) 38.227 ms 38.227 ms 221.176.24.146 (221.176.24.146) 36.254 ms
9 221.176.23.90 (221.176.23.90) 38.256 ms 38.665 ms 38.239 ms
10 223.118.2.213 (223.118.2.213) 40.130 ms 223.118.2.201 (223.118.2.201) 41.462 ms 41.437 ms
11 223.118.2.230 (223.118.2.230) 40.518 ms 40.573 ms 40.500 ms
12 203.131.250.5 (203.131.250.5) 38.969 ms 38.616 ms 38.599 ms
13 ae-7.r23.tkokhk01.hk.bb.gin.ntt.net (129.250.4.26) 38.898 ms 39.377 ms 53.317 ms <--- [香港]
14 ae-12.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.3.88) 90.480 ms 85.739 ms 90.261 ms <--- [日本]
15 ae-5.r02.tokyjp03.jp.bb.gin.ntt.net (129.250.3.251) 92.469 ms 92.444 ms 92.762 ms
16 xe-0-3-0-9.r02.tokyjp03.jp.ce.gin.ntt.net (117.103.177.34) 93.570 ms 107.922 ms 93.416 ms
17 45.63.125.92.vultr.com (45.63.125.92) 90.264 ms 86.860 ms 90.510 ms
18 我家水表

北京联通
------------------------------
traceroute to 我家水表, 30 hops max, 40 byte packets
1 * * *
2 10.81.76.145 (10.81.76.145) 0.475 ms 0.513 ms 0.508 ms
3 123.125.128.5 (123.125.128.5) 0.344 ms 0.528 ms 0.620 ms
4 202.106.34.5 (202.106.34.5) 0.877 ms 0.884 ms 0.875 ms
5 123.126.0.85 (123.126.0.85) 2.839 ms 2.839 ms 2.834 ms
6 219.158.12.58 (219.158.12.58) 26.201 ms 25.940 ms 25.890 ms
7 219.158.97.98 (219.158.97.98) 36.813 ms 37.314 ms 37.276 ms
8 219.158.97.114 (219.158.97.114) 32.234 ms 31.977 ms 31.940 ms
9 219.158.38.98 (219.158.38.98) 54.989 ms 53.098 ms 53.067 ms
10 129.250.7.70 (129.250.7.70) 53.767 ms 129.250.7.74 (129.250.7.74) 98.928 ms 98.895 ms <--- [日本]
11 129.250.3.253 (129.250.3.253) 51.840 ms 51.964 ms 51.966 ms
12 117.103.177.34 (117.103.177.34) 57.183 ms 59.865 ms 55.133 ms
13 45.63.125.92 (45.63.125.92) 98.033 ms 98.905 ms 98.889 ms
14 我家水表

综合上述，三大运营商到日本的路由信息
--------------------------------------------------
电信：骨干 -> 美国 -> 日本 -> 我家水表
移动：骨干 -> 香港 -> 日本 -> 我家水表
联通：骨干 -> 日本 -> 我家水表


我的观点：
-------------
联通貌似有专线直接到日本（香港） NTT ，路由算干净，不过根据实际使用情况，家用宽带晚上延时也会上百，但基本不丢包。

移动宽带用户较少，起步较晚，主要的带宽都花在手机网络上，而这部分带宽很贵，用户会珍惜使用，出国带宽用的人更少了，所以目前出国的质量非常好。

电信就不说了， 163 、 169 、 CN2 、国际精品网，我估计起码会再混乱 3 年以上，家庭、公司新装宽带都不会在考虑。

综合上述，移动 > 联通 > 电信

（思考一个问题：移动互联网时代，你的用户手机运营商主要是 _____，如果流量费 /融合套餐能进一步下降呢？）

监控工具：
-------------
http://jk.cloud.360.cn

已经观察很久了，有图有真相 。。。

http://i13.tietuku.com/7fe627bdae462535.png

http://i13.tietuku.com/a7b445e5a5fba4da.png

test
<img src="http://ww4.sinaimg.cn/bmiddle/e88ee741jw1ew5kcqio78j20zk0jydhw.jpg" />

同问：

Server 侧日志：
------------------------
08[CFG] received stroke: add connection 'windows7'
08[CFG] adding virtual IP address pool 172.17.17.0/24
08[CFG] loaded certificate "C=CN, O=strongSwan, CN=x.x.x.x" from 'serverCert.pem'
08[CFG] id '%any' not confirmed by certificate, defaulting to 'C=CN, O=strongSwan, CN=x.x.x.x'
08[CFG] added configuration 'windows7'
10[NET] received packet: from 210.51.19.2[17553] to x.x.x.x[500] (388 bytes)
10[ENC] parsed IKE_SA_INIT request 0 [ SA KE No N(REDIR_SUP) N(NATD_S_IP) N(NATD_D_IP) N(FRAG_SUP) ]
10[IKE] 210.51.19.2 is initiating an IKE_SA
10[CFG] received proposals: IKE:AES_CBC_128/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024, IKE:AES_CBC_256/HMAC_SHA2_256_128/PRF_HMAC_SHA2_256/MODP_1536, IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024
10[CFG] configured proposals: IKE:AES_CBC_256/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024
10[IKE] remote host is behind NAT
10[IKE] received proposals inacceptable
10[ENC] generating IKE_SA_INIT response 0 [ N(NO_PROP) ]
10[NET] sending packet: from x.x.x.x[500] to *.*.*.* [17553] (36 bytes)

Client 侧日志：
------------------------
Oct 12 11:02:36 Onion-iPhone-6S nesessionmanager[247] <Notice>: NESMIKEv2VPNSession[x.x.x.x:1FECCA55-2070-44C8-8214-E62DF31F6E0B]: status changed to connecting
Oct 12 11:02:36 Onion-iPhone-6S locationd[70] <Notice>: need a scan, count, 0, 0, lwatchdog, 0.0, interval, 60.0, needWatchdog, 0
Oct 12 11:02:36 Onion-iPhone-6S configd[38] <Notice>: network changed
Oct 12 11:02:36 Onion-iPhone-6S neagent[291] <Error>: Failed to process IKE SA Init packet
Oct 12 11:02:36 Onion-iPhone-6S neagent[291] <Notice>: BUG in libdispatch client: kevent[EVFILT_READ] delete: "Bad file descriptor" - 0x9

官方文档，不明觉厉
------------------------
https://wiki.strongswan.org/projects/strongswan/wiki/IOS_(Apple)#IKEv2-on-iOS-9-OS-X-1011-and-newer