CP Posted February 11, 2006 Author CID Share Posted February 11, 2006 W/O ZA and Anti Virus: 2006-02-11 18:11:48 EST: 712 / 132 Your download speed : 712 Kbps or 89 kB/sec. Your upload speed : 132 Kbps or 16.6 kB/sec. =================================== Also: :::.. Download Stats ..::: Connection is:: 737 Kbps about 0.7 Mbps (tested with 748 kB) Download Speed is:: 90 kB/s Tested From:: https://testmy.net (server1) Test Time:: Sat Feb 11 15:13:07 PST 2006 Bottom Line:: 13X faster than 56K 1MB download in 11.38 sec Diagnosis: May need help : running at only 15.65 % of your hosts average (verizon.net) Validation Link:: https://testmy.net/stats/id-V5T2L6E04 and: ============================ :::.. Upload Stats ..::: Connection is:: 137 Kbps about 0.1 Mbps (tested with 97 kB) Upload Speed is:: 17 kB/s Tested From:: https://testmy.net (server1) Test Time:: Sat Feb 11 15:13:42 PST 2006 Bottom Line:: 2X faster than 56K 1MB upload in 60.24 sec Diagnosis: May need help : running at only 21.85 % of your hosts average (verizon.net) Validation Link:: https://testmy.net/stats/id-G9XZ2U708 ==================== Trace: tracert www.testmy.net Tracing route to www.testmy.net [67.18.179.85] over a maximum of 30 hops: 1 19 ms 18 ms 18 ms L100.DSL-34.LSANCA.verizon-gni.net [71.104.202.1 ] 2 19 ms 20 ms 19 ms 130.81.35.90 3 22 ms 20 ms 21 ms so-7-0-0-0.PEER-RTR2.LAX80.verizon-gni.net [130. 81.17.151] 4 21 ms 21 ms 21 ms so-4-3-0-0.gar2.LosAngeles1.Level3.net [4.78.202 .29] 5 21 ms 20 ms 23 ms ae-2-54.bbr2.LosAngeles1.Level3.net [4.68.102.97 ] 6 52 ms 55 ms 52 ms as-1-0.bbr2.Dallas1.Level3.net [64.159.0.245] 7 51 ms 55 ms 52 ms ae-13-53.car3.Dallas1.Level3.net [4.68.122.79] 8 53 ms 53 ms 53 ms 4.78.221.146 9 54 ms 54 ms 56 ms vl32.dsr02.dllstx3.theplanet.com [70.85.127.62] 10 54 ms 55 ms 55 ms vl42.dsr02.dllstx4.theplanet.com [70.85.127.91] 11 55 ms 55 ms 55 ms gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.8 5] 12 55 ms 52 ms 54 ms 85.67-18-179.reverse.theplanet.com [67.18.179.85 ] Trace complete. ====================== TCP/Web100 Network Diagnostic Tool v5.3.3d click START to begin Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 188.00Kb/s running 10s inbound test (server to client) . . . . . . 717.13kb/s Your PC is connected to a Cable/DSL modem Information: The receive buffer should be 451.40 Kbytes to maximize throughput ================================== ------ Web100 Detailed Analysis ------ Cable modem/DSL/T1 link found. Link set to Full Duplex mode No network congestion discovered. Good network cable(s) found Normal duplex operation found. Web100 reports the Round trip time = 1232.65 msec; the Packet size = 1460 Bytes; and No packet loss was observed. This connection is receiver limited 85.26% of the time. Increasing the the client's receive buffer (125.0 KB) will improve performance This connection is network limited 14.71% of the time. Web100 reports TCP negotiated the optional Performance Settings to: RFC 2018 Selective Acknowledgment: ON RFC 896 Nagle Algorithm: ON RFC 3168 Explicit Congestion Notification: OFF RFC 1323 Time Stamping: OFF RFC 1323 Window Scaling: ON Packet size is preserved End-to-End Server IP addresses are preserved End-to-End Client IP addresses are preserved End-to-End ==================================== (SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10] Checking for congestion (cwndtime > .02) [0.14>.02], (mismatch = 0) [0=0] (MaxSsthresh > 0) [0>0] estimate = 9.04 based on packet size = 11Kbits, RTT = 1232.65msec, and loss = 1.0E-6 The theoretical network limit is 9.04 Mbps The NDT server has a 8192.0 KByte buffer which limits the throughput to 51.92 Mbps Your PC/Workstation has a 125.0 KByte buffer which limits the throughput to 0.79 Mbps The network based flow control limits the throughput to 0.80 Mbps Client Data reports link is 'T1', Client Acks report link is 'T1' Server Data reports link is 'T1', Server Acks report link is 'T1' Quote Link to comment Share on other sites More sharing options...
trogers Posted February 12, 2006 CID Share Posted February 12, 2006 estimate = 9.04 based on packet size = 11Kbits, RTT = 1232.65msec, and loss = 1.0E-6 The theoretical network limit is 9.04 Mbps The NDT server has a 8192.0 KByte buffer which limits the throughput to 51.92 Mbps Your PC/Workstation has a 125.0 KByte buffer which limits the throughput to 0.79 Mbps The network based flow control limits the throughput to 0.80 Mbps Your RTT is still too high. This usually means something is limiting a clear signal flow. Can be a line quality problem or a faulty cable, or effects on your signalling devices (modem/router). If you are running a wireless, then it may be a problem with signal transmission to your router. Please do some troubleshooting. When RTT goes down, PC throughput limit will go up and so does your download speed. Here is a link that may help you to located possible line problem: http://www.dslreports.com/faq/faq/8.%20Home%20wiring Quote Link to comment Share on other sites More sharing options...
CP Posted February 12, 2006 Author CID Share Posted February 12, 2006 Thanks for all the help but if it has come down to changing a wire or moving my stuff around for a clear signal flow......... I'm thinking it is not going to jump that high. A lot of trial and no change. Oh well, trogers you really went out of your way to help me and as I said, nothing has worked. Oh well, wonder if cable would be a better alternative for same $. Thanks anyway but chalk this one to a lost cause. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.