Jump to content

Recent latency issues


jdb

Recommended Posts

So a few weeks ago I was experiencing intermittent signals to my modem. After lengthy conversations with Comcast it was determined the was significant packet loss and a tech was sent to my house. He tested the signals outside and inside and said that they were all within "acceptable" range which usually means it could be better, but they do not want to take the time to make it better. Two weeks pass, and I have gone from intermittent signals @ 6.2 Mbps down to intermittent signals @ anywhere from .27Mbps to .34 Mbps down. A lengthy conversation with comcast today resulted in yet another service call. I always check my speeds on this site and have just recently started reading the posts and thread herein. After attempting to troubleshoot and repair this problem myself through cablenut and TCPOptimized, I registered and I am bringing my problems to the boards. Any and all help is greatly appreciated.

I am running Win/XP SP2, have tweaked with cablenut and TCPOptimizer, have run CCleaner, once a week I run spybot s&d, spywareblaster and all updated anitvirus and windows updates. There is definitely no malware spyware or virii on my computer. It seems to be either a cabling issue inside the house or from the pole to the junction box outside. Anyways, here is the results from all tests that I have run and it seems latency/packet loss is my biggest issue. Weird thing is, upstream is now faster than downstream. I suscribe to Comcast 6000/384 and I usually get 6200/380ish and have never had problems like I have recently.

TCP options string = 020405b40103030301010402

MTU = 1500

MTU is fully optimized for broadband.

MSS = 1460

Maximum useful data in each packet = 1460, which equals MSS.

Default TCP Receive Window (RWIN) = 513920

RWIN Scaling (RFC1323) = 3 bits (scale factor of 6)

Unscaled TCP Receive Window = 64240

RWIN is a multiple of MSS

Other RWIN values that might work well with your current MTU/MSS:

513920 (MSS x 44 * scale factor of 8) <-- current value

256960 (MSS x 44 * scale factor of 4)

128480 (MSS x 44 * scale factor of 2)

64240 (MSS x 44)

bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 20556.8 kbps (2569.6 KBytes/s) @ 200ms

Your TCP Window limits you to: 8222.72 kbps (1027.84 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 54 hops

TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349) = 00100000 (32)

Precedence (priority) = 001 (priority)

Delay = 0 (normal delay)

Throughput = 0 (normal throughput)

Reliability = 0 (normal reliability)

Cost = 0 (normal cost)

Check bit = 0 (correct, 8th checking bit must be zero)

DiffServ (RFC 2474) = CS1 001000 (8) - class 1 (RFC 2474). Similar forwarding behavior to the ToS Precedence field.

--------------------------------------------------------------------------------------------------------------------

The current date is: Sat 09/16/2006

The current time is: 21:59:40.32

Microsoft Windows XP [Version 5.1.2600]

Pinging testmy.net [67.18.179.85] with 32 bytes of data:

Request timed out.

Reply from 67.18.179.85: bytes=32 time=31ms TTL=53

Reply from 67.18.179.85: bytes=32 time=52ms TTL=53

Reply from 67.18.179.85: bytes=32 time=49ms TTL=53

Reply from 67.18.179.85: bytes=32 time=58ms TTL=53

Reply from 67.18.179.85: bytes=32 time=53ms TTL=53

Reply from 67.18.179.85: bytes=32 time=53ms TTL=53

Reply from 67.18.179.85: bytes=32 time=49ms TTL=53

Reply from 67.18.179.85: bytes=32 time=48ms TTL=53

Reply from 67.18.179.85: bytes=32 time=50ms TTL=53

Reply from 67.18.179.85: bytes=32 time=55ms TTL=53

Reply from 67.18.179.85: bytes=32 time=49ms TTL=53

Ping statistics for 67.18.179.85:

    Packets: Sent = 12, Received = 11, Lost = 1 (8% loss),

Approximate round trip times in milli-seconds:

    Minimum = 31ms, Maximum = 58ms, Average = 49ms

Ping Complete.

--------------------------------------------------------------------------------------------------------------------

Tracing route to testmy.net [67.18.179.85]

over a maximum of 30 hops:

  1    10 ms    9 ms    11 ms  xx.xx.xx.x

  2    28 ms    29 ms    *    s01b1.bartlett.ga.savannah.comcast.net [xx.xx.xxx.xx]

  3    9 ms    8 ms    10 ms  s01g1.savannah.ga.savannah.comcast.net [xx.xx.xxx.xx]

  4    36 ms    36 ms    *    12.124.64.25

  5    *      55 ms    57 ms  tbr2-p013801.attga.ip.att.net [12.123.20.174]

  6    51 ms    *        *    tbr1-cl13.dlstx.ip.att.net [12.122.2.89]

  7    46 ms    36 ms    37 ms  gar1-p340.dlrtx.ip.att.net [12.123.16.161]

  8    41 ms    32 ms    32 ms  12.119.136.14

  9    *        *      51 ms  vl32.dsr01.dllstx3.theplanet.com [70.85.127.61]

10    50 ms    53 ms    49 ms  vl42.dsr02.dllstx4.theplanet.com [70.85.127.91]

11    56 ms    *      59 ms  gi1-0-1.car17.dllstx4.theplanet.com [67.18.116.69]

12    48 ms    55 ms    51 ms  55.b3.1243.static.theplanet.com [67.18.179.85]

Trace complete.

--------------------------------------------------------------------------------------------------------------------

:::.. testmy.net test results ..:::

Download Connection is:: 264 Kbps about 0.26 Mbps (tested with 386 kB)

Download Speed is:: 32 kB/s

Upload Connection is:: 379 Kbps about 0.38 Mbps (tested with 748 kB)

Upload Speed is:: 46 kB/s

Tested From:: https://testmy.net (Server 1)

Test Time:: 2006/09/16 - 7:05pm

D-Validation Link:: https://testmy.net/stats/id-FYD5J86IT

U-Validation Link:: https://testmy.net/stats/id-1UTGVC453

User Agent:: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7 [!]

--------------------------------------------------------------------------------------------------------------------

WEB100 Enabled Statistics:

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 399.49Kb/s

running 10s inbound test (server to client) . . . . . . 120.72kb/s

--------------------------------------------------------------------------------------------------------------------

------  Client System Details  ------

OS data: Name = Windows XP, Architecture = x86, Version = 5.1

Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06

------  Web100 Detailed Analysis  ------

Cable modem/DSL/T1 link found.

Link set to Full Duplex mode

Information: throughput is limited by other network traffic.

Good network cable(s) found

Normal duplex operation found.

Web100 reports the Round trip time = 179.19 msec; the Packet size = 1460 Bytes; and

There were 17 packets retransmitted, 20 duplicate acks received, and 22 SACK blocks received

The connection stalled 2 times due to packet loss

The connection was idle 0.86 seconds (8.6%) of the time

This connection is network limited 99.96% of the time.

Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

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

Information: Network Address Translation (NAT) box is modifying the Client's IP address

Server says [xx.xx.xx.xxx] but Client says [192.168.1.101]

--------------------------------------------------------------------------------------------------------------------

WEB100 Kernel Variables:

Client: localhost/127.0.0.1

AckPktsIn: 72

AckPktsOut: 0

BytesRetrans: 24820

CongAvoid: 28

CongestionOverCount: 0

CongestionSignals: 9

CountRTT: 37

CurCwnd: 5840

CurMSS: 1460

CurRTO: 430

CurRwinRcvd: 513920

CurRwinSent: 16304

CurSsthresh: 2920

DSACKDups: 0

DataBytesIn: 0

DataBytesOut: 185420

DataPktsIn: 0

DataPktsOut: 127

DupAcksIn: 20

ECNEnabled: 0

FastRetran: 6

MaxCwnd: 7300

MaxMSS: 1460

MaxRTO: 540

MaxRTT: 300

MaxRwinRcvd: 513920

MaxRwinSent: 16304

MaxSsthresh: 2920

MinMSS: 1460

MinRTO: 330

MinRTT: 110

MinRwinRcvd: 64240

MinRwinSent: 16304

NagleEnabled: 1

OtherReductions: 0

PktsIn: 72

PktsOut: 127

PktsRetrans: 17

X_Rcvbuf: 103424

RcvWinScale: 7

SACKEnabled: 3

SACKsRcvd: 22

SendStall: 0

SlowStart: 13

SampleRTT: 110

SmoothedRTT: 170

X_Sndbuf: 103424

SndWinScale: 3

SndLimTimeRwin: 0

SndLimTimeCwnd: 10564644

SndLimTimeSender: 4256

SndLimTransRwin: 0

SndLimTransCwnd: 1

SndLimTransSender: 1

SndLimBytesRwin: 0

SndLimBytesCwnd: 185420

SndLimBytesSender: 0

SubsequentTimeouts: 1

SumRTT: 6630

Timeouts: 2

TimestampsEnabled: 0

WinScaleRcvd: 3

WinScaleSent: 7

DupAcksOut: 0

StartTimeUsec: 792956

Duration: 10575031

c2sData: 2

c2sAck: 2

s2cData: 9

s2cAck: 2

half_duplex: 0

link: 100

congestion: 1

bad_cable: 0

mismatch: 0

spd: 0.00

bw: 0.23

loss: 0.070866142

avgrtt: 179.19

waitsec: 0.86

timesec: 10.00

order: 0.2778

rwintime: 0.0000

sendtime: 0.0004

cwndtime: 0.9996

rwin: 3.9209

swin: 64.0000

cwin: 0.0557

rttsec: 0.179189

Sndbuf: 8388608

aspd: 0.46080

Checking for mismatch on uplink

(speed > 50 [0>50], (xmitspeed < 5) [0.39<5]

(rwintime > .9) [0>.9], (loss < .01) [0.07<.01]

Checking for excessive errors condition

(loss/sec > .15) [0.00>.15], (cwndtime > .6) [0.99>.6],

(loss < .01) [0.07<.01], (MaxSsthresh > 0) [2920>0]

Checking for 10 Mbps link

(speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]

(xmitspeed < 9.5) [0.39<9.5] (loss < .01) [0.07<.01], (mylink > 0) [3.0>0]

Checking for Wireless link

(sendtime = 0) [4.0E=0], (speed < 5) [0<5]

(Estimate > 50 [0.23>50], (Rwintime > 90) [0>.90]

(RwinTrans/CwndTrans = 1) [0/1=1], (mylink > 0) [3.0>0]

Checking for DSL/Cable Modem link

(speed < 2) [0<2], (SndLimTransSender = 0) [1=0]

(SendTime = 0) [4.0E-4=0], (mylink > 0) [3.0>0]

Checking for half-duplex condition

(rwintime > .95) [0>.95], (RwinTrans/sec > 30) [0>30],

(SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]

Checking for congestion

(cwndtime > .02) [0.99>.02], (mismatch = 0) [0=0]

(MaxSsthresh > 0) [2920>0]

estimate = 0.23 based on packet size = 11Kbits, RTT = 179.19msec, and loss = 0.070866142

The theoretical network limit is 0.23 Mbps

The NDT server has a 8192.0 KByte buffer which limits the throughput to 357.16 Mbps

Your PC/Workstation has a 501.0 KByte buffer which limits the throughput to 21.88 Mbps

The network based flow control limits the throughput to 0.31 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'

Server Data reports link is '10 Gig', Server Acks report link is 'T1'

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Some earlier latency tests through the newest TCPOptimizer program were reporting packet losses ranging from 3% up to 40%. Any suggestions why I am having such inconsistent packet loss and low downstream speeds? It seems that upstream is unaffected. Thank you in advance for any and all help.

Link to comment
Share on other sites

So I was reading aznhakkaboi's thread suggesting someone uncapped their modem and is sucking up the bandwidth for that area. I am usually not using my internet until later in the evening so I have never noticed such crappy speeds. So after reading his post I thought I would wait until later at night to retest speed and voila!! Here is my latest results.

Test Result Details

Your connection is: 6389 Kbps or 6.39 Mbps

You Downloaded at: 780 kB/s

You are running: 111 times faster than 56K and can Download 1 megabyte in 1.31 second(s)

Member Ident:Username:jdb CompID:653205889219

Test Time:: 2006/09/16 - 9:53pm

Test Browser and OS info: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7

Test ID: 2ARTX8PH0 (if this is a screenshot go to testmy.net to see if this is fake)

Diagnosis ^info^: Looks Great : 15.68 % faster than the average for host (comcast.net)

This was tested from a 5983 kB file and took 7.672 seconds to complete

Link to comment
Share on other sites

Thought I would check latency while I am on TMN and it appears absolutely NO latency or packet loss. Could this just be a peak-time issue? Or someone sucking up bandwidth? Sorry for repetitive posts, just looking for some clarity.

Pinging [193.10.252.19] with 64 bytes ->bytes=64 time=128ms TTL=241

Pinging [193.10.252.19] with 64 bytes ->bytes=64 time=128ms TTL=241

Pinging [193.10.252.19] with 64 bytes ->bytes=64 time=137ms TTL=241

Pinging [193.10.252.19] with 64 bytes ->bytes=64 time=127ms TTL=241

Pinging [193.10.252.19] with 64 bytes ->bytes=64 time=128ms TTL=241

Pinging [193.10.252.19] with 64 bytes ->bytes=64 time=127ms TTL=241

Pinging [193.10.252.19] with 64 bytes ->bytes=64 time=137ms TTL=241

Pinging [193.10.252.19] with 64 bytes ->bytes=64 time=128ms TTL=241

Pinging [193.10.252.19] with 64 bytes ->bytes=64 time=137ms TTL=241

Pinging [218.32.192.112] with 64 bytes ->bytes=64 time=241ms TTL=49

Pinging [218.32.192.112] with 64 bytes ->bytes=64 time=245ms TTL=49

Pinging [218.32.192.112] with 64 bytes ->bytes=64 time=240ms TTL=49

Pinging [218.32.192.112] with 64 bytes ->bytes=64 time=239ms TTL=49

Pinging [218.32.192.112] with 64 bytes ->bytes=64 time=239ms TTL=49

Pinging [218.32.192.112] with 64 bytes ->bytes=64 time=239ms TTL=49

Pinging [218.32.192.112] with 64 bytes ->bytes=64 time=241ms TTL=49

Pinging [218.32.192.112] with 64 bytes ->bytes=64 time=240ms TTL=49

Pinging [218.32.192.112] with 64 bytes ->bytes=64 time=239ms TTL=49

Pinging [204.127.135.135] with 64 bytes ->bytes=64 time=36ms TTL=54

Pinging [204.127.135.135] with 64 bytes ->bytes=64 time=36ms TTL=54

Pinging [204.127.135.135] with 64 bytes ->bytes=64 time=36ms TTL=54

Pinging [204.127.135.135] with 64 bytes ->bytes=64 time=36ms TTL=54

Pinging [204.127.135.135] with 64 bytes ->bytes=64 time=41ms TTL=54

Pinging [204.127.135.135] with 64 bytes ->bytes=64 time=35ms TTL=54

Pinging [204.127.135.135] with 64 bytes ->bytes=64 time=36ms TTL=54

Pinging [204.127.135.135] with 64 bytes ->bytes=64 time=35ms TTL=54

Pinging [204.127.135.135] with 64 bytes ->bytes=64 time=35ms TTL=54

Pinging [207.155.252.68] with 64 bytes ->bytes=64 time=97ms TTL=240

Pinging [207.155.252.68] with 64 bytes ->bytes=64 time=105ms TTL=240

Pinging [207.155.252.68] with 64 bytes ->bytes=64 time=96ms TTL=240

Pinging [207.155.252.68] with 64 bytes ->bytes=64 time=97ms TTL=240

Pinging [207.155.252.68] with 64 bytes ->bytes=64 time=97ms TTL=240

Pinging [207.155.252.68] with 64 bytes ->bytes=64 time=97ms TTL=240

Pinging [207.155.252.68] with 64 bytes ->bytes=64 time=98ms TTL=240

Pinging [207.155.252.68] with 64 bytes ->bytes=64 time=97ms TTL=240

Pinging [207.155.252.68] with 64 bytes ->bytes=64 time=99ms TTL=240

Pinging [63.217.30.70] with 64 bytes ->bytes=64 time=33ms TTL=51

Pinging [63.217.30.70] with 64 bytes ->bytes=64 time=36ms TTL=51

Pinging [63.217.30.70] with 64 bytes ->bytes=64 time=34ms TTL=51

Pinging [63.217.30.70] with 64 bytes ->bytes=64 time=33ms TTL=51

Pinging [63.217.30.70] with 64 bytes ->bytes=64 time=36ms TTL=51

Pinging [63.217.30.70] with 64 bytes ->bytes=64 time=32ms TTL=51

Pinging [63.217.30.70] with 64 bytes ->bytes=64 time=35ms TTL=51

Pinging [63.217.30.70] with 64 bytes ->bytes=64 time=33ms TTL=51

Pinging [63.217.30.70] with 64 bytes ->bytes=64 time=33ms TTL=51

Ping statistics for above hosts:

  Packets: Sent = 45, Received = 45, Lost = 0 (0% loss)

Approximate round trip times (RTT) in milli-seconds:

  Minimum = 32ms, Maximum =  245ms, Average =  107ms

Link to comment
Share on other sites

Download Connection is:: 264 Kbps about 0.26 Mbps (tested with 386 kB)

Your connection is: 6389 Kbps or 6.39 Mbps

Interesting, and they were like 2 hours apart.

So are you using the smart test?

Try this and clear yourtemp files before clicking the link, asit takes you directly to the test.

http://www.testmy.net/tools/test/d_load.php?ni=1&tt=1&s=5983&st=st

You might also try it with out the router, unless it is necesary for your ISP.

Link to comment
Share on other sites

Yes I use the SmarTest and have tested speeds on this site for over 2 years, always the best and extremely accurate. I clear all cache and temp files when I close my browser. Like you said, such a huge difference in just a few hours. 90% of the time I test my speed here it is 6.2 - 6.4Mbps. I had today off and decided to play DAoC and kept going link-dead. Tested speed and that is when i got the .27 - .34 Mbps. I wonder if someone in my neighborhood has uncapped their modem and sucking all the bandwidth. How possible is that? I have no experience with uncapping a modem and read somewhere uncapping a modem can rarely do things as the modem itself usually has a 10Mbps cap itself anyways. I thank you for your responses and input greatly.

Link to comment
Share on other sites

Cleared cache and temp files and clicked your link. By far the fastest speed I have seen since I have had comcast.

Your connection is: 6508 Kbps or 6.51 Mbps

You Downloaded at: 794 kB/s

You are running: 113 times faster than 56K and can Download 1 megabyte in 1.29 second(s)

Member Ident:Username:jdb CompID:653205889219

Test Time:: 2006/09/16 - 10:40pm

Test Browser and OS info: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7

Test ID: HWZKQTN56 (if this is a screenshot go to testmy.net to see if this is fake)

Diagnosis ^info^: Looks Great : 17.81 % faster than the average for host (comcast.net)

This was tested from a 5983 kB file and took 7.532 seconds to complete

Link to comment
Share on other sites

Router is not necessary for my ISP, but earlier today I connected directly to the cable modem and got the same results. Comcast saw significant packet losses as did I with latency tests. But would someone "stealing" bandwidth cause packet losses? I thought packet loss was attributed to bad cabling or problems with TCP/IP. Did not think bandwidth affected latency. Makes me think it is something on Comcast's side and not my hardware/software.

Link to comment
Share on other sites

Cleared cache and temp files and clicked your link. By far the fastest speed I have seen since I have had comcast.

Your connection is: 6508 Kbps or 6.51 Mbps

You Downloaded at: 794 kB/s

You are running: 113 times faster than 56K and can Download 1 megabyte in 1.29 second(s)

Member Ident:Username:jdb CompID:653205889219

Test Time:: 2006/09/16 - 10:40pm

Test Browser and OS info: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7

Test ID: HWZKQTN56 (if this is a screenshot go to testmy.net to see if this is fake)

Diagnosis ^info^: Looks Great : 17.81 % faster than the average for host (comcast.net)

This was tested from a 5983 kB file and took 7.532 seconds to complete

if you clrear your cache do you get that result every time you do it?

Link to comment
Share on other sites

jdb ;Try the NDT Web 100 test again when your are getting the better speed with the testmy test.These results indicate problems & I wanted to see what it says when your running at your better speed.

Web100 reports the Round trip time = 179.19 msec; the Packet size = 1460 Bytes; and

There were 17 packets retransmitted, 20 duplicate acks received, and 22 SACK blocks received

The connection stalled 2 times due to packet loss

The connection was idle 0.86 seconds (8.6%) of the time

This connection is network limited 99.96% of the time.

Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

Information: Network Address Translation (NAT) box is modifying the Client's IP address

   Server says [xx.xx.xx.xxx] but Client says [192.168.1.101]

These look almost like my dial -up

The theoretical network limit is 0.23 Mbps

The network based flow control limits the throughput to 0.31 Mbps

Here's the same areas with my dial-up:

Web100 reports the Round trip time = 739.82 msec; the Packet size = 1460 Bytes; and

No packet loss was observed.

This connection is receiver limited 82.48% of the time.

  Increasing the current receive buffer (11.0 KB) will improve performance

This connection is network limited 17.39% of the time.

  Contact your local network administrator to report a network problem

Packet size is preserved End-to-End

Server IP addresses are preserved End-to-End

Client IP addresses are preserved End-to-End

bw = 15.05 based on packet size = 11Kbits, RTT = 739.82msec, and loss = 1.0E-6

The theoretical network limit is 15.05 Mbps

The network based flow control limits the application to 0.13 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'

Server Data reports link is 'OC-12', Server Acks report link is 'T1'

The theoretical network limit is 0.23 Mbps

The network based flow control limits the throughput to 0.31 Mbps

If I could get the limit of 0.13 Mbps I would be very happy but since that's not possible with dial-up the limit is not a problem for me.It would be a problem for your connection.

Heres a couple of testmy tests I ran this morning.there a bit too fast but this shows I was reaching top dial-up speed.

:::.. Download Stats ..:::

Download Connection is:: 83 Kbps about 0.08 Mbps (tested with 97 kB)

Download Speed is:: 10 kB/s

Tested From:: https://testmy.net/ (Server 1)

Test Time:: 2006/09/18 - 7:20am

Bottom Line:: 1X faster than 56K 1MB Download in 102.4 sec

Tested from a 97 kB file and took 9.56 seconds to complete

Download Diagnosis:: May need help : running at only 7.44 % of your hosts average (nts-online.net)

D-Validation Link:: https://testmy.net/stats/id-DWG5ZC3Q6

User Agent:: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90) [!]

:::.. Download Stats ..:::

Download Connection is:: 65 Kbps about 0.07 Mbps (tested with 97 kB)

Download Speed is:: 8 kB/s

Tested From:: https://testmy.net/ (Server 1)

Test Time:: 2006/09/18 - 7:21am

Bottom Line:: 1X faster than 56K 1MB Download in 128 sec

Tested from a 97 kB file and took 12.08 seconds to complete

Download Diagnosis:: May need help : running at only 5.83 % of your hosts average (nts-online.net)

D-Validation Link:: https://testmy.net/stats/id-7X154RTMZ

User Agent:: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90) [!]

Link to comment
Share on other sites

Heres a couple of testmy tests I ran this morning.there a bit too fast but this shows I was reaching top dial-up speed.

:::.. Download Stats ..:::

Download Connection is:: 83 Kbps about 0.08 Mbps (tested with 97 kB)

Download Speed is:: 10 kB/s

Tested From:: https://testmy.net/ (Server 1)

Test Time:: 2006/09/18 - 7:20am

Bottom Line:: 1X faster than 56K 1MB Download in 102.4 sec

Tested from a 97 kB file and took 9.56 seconds to complete

Download Diagnosis:: May need help : running at only 7.44 % of your hosts average (nts-online.net)

D-Validation Link:: https://testmy.net/stats/id-DWG5ZC3Q6

User Agent:: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90) [!]

:::.. Download Stats ..:::

Download Connection is:: 65 Kbps about 0.07 Mbps (tested with 97 kB)

Download Speed is:: 8 kB/s

Tested From:: https://testmy.net/ (Server 1)

Test Time:: 2006/09/18 - 7:21am

Bottom Line:: 1X faster than 56K 1MB Download in 128 sec

Tested from a 97 kB file and took 12.08 seconds to complete

Download Diagnosis:: May need help : running at only 5.83 % of your hosts average (nts-online.net)

D-Validation Link:: https://testmy.net/stats/id-7X154RTMZ

User Agent:: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90) [!]

how are you getting those speeds off dial-up when a phone modem can only go to max 53kbps

Link to comment
Share on other sites

He is taking over for ROM-DOS on dial-up. Someone had to do it.

Check out some of ROM's old speed post's. They were way over 100 kbps. And no modem bonding. And also on free dial-up.

Very few actually know how he did it.

Here is a couple of his good ones.

:::.. Download Stats ..:::

Connection is:: 65 Kbps about 0.1 Mbps (tested with 386 kB)

Download Speed is:: 8 kB/s

Tested From:: https://testmy.net/ (server2)

Test Time:: Sat Nov 12 18:13:38 PST 2005

Bottom Line:: 1X faster than 56K 1MB download in 128 sec

Diagnosis: May need help : running at only 84.42 % of your hosts average (nocharge.com)

Validation Link:: https://testmy.net/stats/id-KY9OWIBCS

:::.. Download Stats ..:::

Connection is:: 187 Kbps about 0.2 Mbps (tested with 97 kB)

Download Speed is:: 23 kB/s

Tested From:: https://testmy.net/ (server2)

Test Time:: Sat Nov 12 18:16:26 PST 2005

Bottom Line:: 3X faster than 56K 1MB download in 44.52 sec

Diagnosis: Awesome! 20% + : 142.86 % faster than the average for host (nocharge.com)

Validation Link:: https://testmy.net/stats/id-RJ98N0OSK

:haha: :haha: :haha:

Believe it or not, few did!

Link to comment
Share on other sites

dlewis23 :That's why I said the tests were too fast.The small test the smart test uses for dial up has this kind of speed burst sometimes.On a larger test it will even out a be slower.But it is not a cached test because what's the point of that.Dial-up can'T do a cached test on the main testmy server.I tried & at one time I could but CA3LE fixed that.I think I can do one on the mirrors or could 6 or 8 months ago.That's the last time I tried.

Rom-Dos's dial-up speed is different he had XP & was very close to the CO.He had consistently very fast speeds even with larger tests.

On mine I make no claim that mine actually exceed the 53Kbps only that when the test shows faster I'm probably getting 53Kbps.Which is excellent since I'm 26529 feet from the CO according to SBC the telephone company I use.I will see if I can do a cached test at a mirror & post it but I will indicate that's what it is.

tommie;I had some old tests that were fast also but I don't know if they may have been cached or partly cached by the time I learned how to do a cached test correctly it produced a lot faster results. Any way I may add some to this just to let y'all have a look.

This is a cached test from one of your mirror sites dlewis23 & used only for an example.I hate to do them because the mess up my stats.

:::.. Download Stats ..:::

Download Connection is:: 8962 Kbps about 8.96 Mbps (tested with 20972 kB)

Download Speed is:: 1094 kB/s

Tested From:: http://theamericanforce.com

Test Time:: 2006/09/18 - 11:04pm

Bottom Line:: 156X faster than 56K 1MB Download in 0.94 sec

Tested from a 20972 kB file and took 19.17 seconds to complete

Download Diagnosis:: Awesome! 20% + : 703.05 % faster than the average for host (nts-online.net)

D-Validation Link:: https://testmy.net/stats/id-NEFOL7IBM

User Agent:: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90) [!]

dlewis23;Check out this old topic made not long after I became a member.

http://www.testmy.net/forum/index.php?topic=1739.0

Link to comment
Share on other sites

tommie;I could do it not logged in but I wanted it have a validation link.

For the other it puts it in my stats then if someone looks at it they don't know I posted it as a cached test.Then if they have dial-up I have to explain that I actually didn't get that speed.

Then this: Download Diagnosis:: Awesome! 20% + : 703.05 % faster than the average for host (nts-online.net)

Next time it will say I'm about 3% of nts-online.net average.No big deal but I like to keep them like they really are.

It's funny that the main testmy servers 1 or 2 won't let the cached test work for me anyway but the mirrors will.

Link to comment
Share on other sites

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.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...