Secret DC business series three test the true bandwidth quality

through the last "secret IDC business – the computer room, the price difference is so big", we understand the difference in bandwidth quality, directly leading to the computer room price difference. So, how can we test the true bandwidth quality? Today, we use some of the most common windows tools to test the bandwidth quality of your computer.

1, TraceRT

In a previous article in

, we mentioned that the quality of the bandwidth directly connected to the backbone is much better than the network connected to the province. When my website main customers from Guangzhou and Shanghai, if my room is connected directly to the backbone network, so when the network flow for customer visit is "Guangzhou -> backbone network node; node", as long as go jump can be achieved; if my room is connected with the Hebei Langfang bandwidth, so when the network flow of customer visits when is the "Guangzhou node -> backbone network node; -> Beijing District of Hebei province node node -> -> Langfang node, need to walk four jump to achieve speed, certainly more than the backbone network access mode has slowed down a lot. TraceRT is used to detect the number of hops and response time from the end customer to the server’s computer room.

method: log into your server and enter in Windows’s Dos interface (start menu run run " cmd"); " tracert -d [IP]" all over the country;

example: login to a three line server 211.166.XXX.XXX, test the following circumstances,

(thanks to the data center backbone network with interesting line bandwidth for

test room)

, tracert, -d, 202.106.196.1, Beijing Unicom connection situation 7 jump (room – Unicom backbone – Beijing Unicom)

, tracert, -d, 122.193.0.10, Jiangsu Unicom connection situation 10 jump (room – Unicom backbone – Jiangsu Unicom)

, tracert, -d, 221.207.59.131, Qinghai Unicom connection situation 9 jump (room – Unicom backbone – Qinghai Unicom)

tracert -d 220.181.22.226 Telecom connectivity 10 jump (room – Telecommunications backbone – Beijing Telecom),

tracert -d 219.137.167.204 Telecom connectivity 11 jump (room – Telecommunications backbone – Guangzhou Telecom),

tracert -d 61.132.74.48 Telecom connectivity 13 jump (room – Telecommunications backbone – Jiangsu Telecom),

tracert -d 211.139.145.1>

through the last "secret IDC business – the computer room, the price difference is so big", we understand the difference in bandwidth quality, directly leading to the computer room price difference. So, how can we test the true bandwidth quality? Today, we use some of the most common windows tools to test the bandwidth quality of your computer.

1, TraceRT

In a previous article in

, we mentioned that the quality of the bandwidth directly connected to the backbone is much better than the network connected to the province. When my website main customers from Guangzhou and Shanghai, if my room is connected directly to the backbone network, so when the network flow for customer visit is "Guangzhou -> backbone network node; node", as long as go jump can be achieved; if my room is connected with the Hebei Langfang bandwidth, so when the network flow of customer visits when is the "Guangzhou node -> backbone network node; -> Beijing District of Hebei province node node -> -> Langfang node, need to walk four jump to achieve speed, certainly more than the backbone network access mode has slowed down a lot. TraceRT is used to detect the number of hops and response time from the end customer to the server’s computer room.

method: log into your server and enter in Windows’s Dos interface (start menu run run " cmd"); " tracert -d [IP]" all over the country;

example: login to a three line server 211.166.XXX.XXX, test the following circumstances,

(thanks to the data center backbone network with interesting line bandwidth for

test room)

, tracert, -d, 202.106.196.1, Beijing Unicom connection situation 7 jump (room – Unicom backbone – Beijing Unicom)

, tracert, -d, 122.193.0.10, Jiangsu Unicom connection situation 10 jump (room – Unicom backbone – Jiangsu Unicom)

, tracert, -d, 221.207.59.131, Qinghai Unicom connection situation 9 jump (room – Unicom backbone – Qinghai Unicom)

tracert -d 220.181.22.226 Telecom connectivity 10 jump (room – Telecommunications backbone – Beijing Telecom),

tracert -d 219.137.167.204 Telecom connectivity 11 jump (room – Telecommunications backbone – Guangzhou Telecom),

tracert -d 61.132.74.48 Telecom connectivity 13 jump (room – Telecommunications backbone – Jiangsu Telecom),

tracert -d 211.139.145.1>

Leave a Reply

Your email address will not be published. Required fields are marked *