1 頁 (共 1 頁)

6/16~6/18 連線緩慢??

文章發表於: 2008年 7月 18日, 02:01
qazxcdews88
6/16開始 至今

主機一直發生連線緩慢的問題

因為本人前幾天有事情再忙

所以沒時間去做測試

剛剛我在做 ping 測試的時候

發現會一直有掉封包的問題

我想這就是連線緩慢的原因吧

而且就算 ping 到....

速度也是30~48ms (正常是23ms~24ms)

然後再做 tracert 的測試

最後一個節點,

也就是我們主機.....

會有掉封包的情況機率有53% (很高....

並來回做了900次 tracert ....

以下式報告結果

圖檔

文章發表於: 2008年 7月 18日, 02:08
qazxcdews88
直接對主機 ping 測試

>ping h532.net -t


Pinging h532.net [220.229.224.203] with 32 bytes of data:

Reply from 220.229.224.203: bytes=32 time=23ms TTL=50
Reply from 220.229.224.203: bytes=32 time=26ms TTL=50
Reply from 220.229.224.203: bytes=32 time=23ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

文章發表於: 2008年 7月 18日, 02:20
qazxcdews88
我剛剛有打電話到中華電信

然後客服在機房端請人測試

他說他們機房內部也這樣

而且經過tracet以後都是出在我們的主機上

掉封包的機率有51%~53%

因為機率太高.....

不然是否可以重開機看看!

謝謝

文章發表於: 2008年 7月 18日, 02:27
joe
您好:
關於您的問題回復如下
1.中華電信對速博的PING值大約為30~48ms 並非您說的23ms~24ms您指的應該是中華對中華的PING值
您可ping
http://www.sparqnet.net
2.您所說的掉封包是因為位置主機端安裝防火牆擋掉tracert及PING,主機最後一各節點才會出現Request timed out.,先關防火牆文章您可參考坊間書籍及搜尋GOOGLE
3.目前觀察您的網站並沒有任何緩慢的情形,您可檢查您本地端的限路況

文章發表於: 2008年 7月 18日, 02:33
qazxcdews88
joe 寫:您好:
關於您的問題回復如下
1.中華電信對速博的PING值大約為30~48ms 並非您說的23ms~24ms您指的應該是中華對中華的PING值
您可ping
http://www.sparqnet.net
2.您所說的掉封包是因為位置主機端安裝防火牆擋掉tracert及PING,主機最後一各節點才會出現Request timed out.,先關防火牆文章您可參考坊間書籍及搜尋GOOGLE
3.目前觀察您的網站並沒有任何緩慢的情形,您可檢查您本地端的限路況


我很確定

因為我以前有做過這樣的動作

都是在24ms左右而已

連網咖專線甚至可以到達13ms

現在掉封包的機率真的很大

我很確定.....

以前根本沒掉過封包......



我因為每天要預覽10000多次頁面

所以預覽的速度都很快

所以有點緩慢(可能1~2s)我都感覺得出來!



[HTML]
Reply from 220.229.224.203: bytes=32 time=36ms TTL=52
Reply from 220.229.224.203: bytes=32 time=41ms TTL=52
Reply from 220.229.224.203: bytes=32 time=25ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Request timed out.
Request timed out.
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Request timed out.
Request timed out.
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=25ms TTL=52
Reply from 220.229.224.203: bytes=32 time=27ms TTL=52
Request timed out.
Request timed out.
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=29ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Request timed out.
Request timed out.
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Request timed out.
Request timed out.
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Request timed out.
Request timed out.
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Request timed out.
Request timed out.
Reply from 220.229.224.203: bytes=32 time=26ms TTL=52
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Request timed out.
Request timed out.
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=31ms TTL=52
Request timed out.
Request timed out.
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Request timed out.
Request timed out.
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=60ms TTL=52
Reply from 220.229.224.203: bytes=32 time=25ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
[/HTML]

文章發表於: 2008年 7月 18日, 02:38
qazxcdews88
再給你看一個資料

這是我在南京那裏的網咖(戰略高手)

裡的電腦鎖測出來的資料

圖檔

不鼓是在哪台主機

反應值都是在9ms....

真的是有問題

我以前是租用美國的主機

也才掉20%而已

台灣主機照理講是不會掉的

而且

如果我是因為防火牆而讓她掉 ping

讓我在 tracet 其他的主機照常理講也是會掉ping的

文章發表於: 2008年 7月 18日, 13:48
qazxcdews88
今天就好很多了!

[HTML]>ping h532.net -t


Pinging h532.net [220.229.224.203] with 32 bytes of data:

Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203 bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=25ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=29ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=23ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
Reply from 220.229.224.203: bytes=32 time=24ms TTL=52
[/HTML]

而且反應都在24ms左右!