Weird Speed Results InsightBB, XP, Vista

Get help and discuss anything related to tweaking your internet connection, as well as the different tools and registry patches on the site. TCP Optimizer settings and Analyzer results should be posted here.
Post Reply
dlsayremn
Member
Posts: 85
Joined: Mon May 15, 2006 10:05 am
Location: Minneapolis, MN

Weird Speed Results InsightBB, XP, Vista

Post by dlsayremn »

InsightBB 20/1.5 Mbps Service.

XP computer old Gateway Essential 667 upgraded from 98SE.
512 MB Ram
Wireless - Trendnet B/G TEW-423PI PCI Card (no ethernet)
Used TCP/IP Optimizer v. 3.0.3.0 with MTU of 1446.

Vista computer Compaq Presario SR2180NX
Wireless - Belkin USB 802.11N 8810-00212 F7D1101 v.1000

Modem - Arrris Touchstone TM602G/P2/NA-8
Router - Belkin 802.11 B/G F5F7234-4 v.1000
Default MTU for th e modem is 1446 and can not be changed in autoconfigure mode.

Problem: Tests at Insight's Louisville2 server shows down speeds about 20 Mbps for both computers. Tests outside Insight shows Vista about 20 Mbps, XP adout 5.0 Mbps.


« SpeedGuide.net TCP Analyzer Results » for XP
Tested on: 09.02.2010 00:50
IP address: 96.28.xx.xxx
Client OS: Windows XP

TCP options string: 0204057e0103030401010402
MSS: 1406
MTU: 1446
TCP Window: 1034816 (multiple of MSS)
RWIN Scaling: 4 bits (2^4=16)
Unscaled RWIN : 64676
Recommended RWINs: 64676, 129352, 258704, 517408, 1034816
BDP limit (200ms): 41393kbps (5174KBytes/s)
BDP limit (500ms): 16557kbps (2070KBytes/s)
MTU Discovery: OFF
TTL: 55
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)


XP at Insight:
Your Download Speed = 20.30Mbps or 2.53MBytes/sec
Your Upload Speed = 1.38Mbps or 177.32KBytes/sec
Average round trip time = 114.43ms

WEB100 Enabled Statistics:

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_21

------ Web100 Detailed Analysis ------
10 Mbps Ethernet link found.
Link set to Half Duplex mode
No network congestion discovered.
Good network cable(s) found

Web100 reports the Round trip time = 114.43 msec; the Packet size = 1406 Bytes; and
There were 5 packets retransmitted, 308 duplicate acks received, and 306 SACK blocks received
The connection was idle 0 seconds (0%) of the time
This connection is network limited 99.52% of the time.

The following TCP settings were detected:
TCP Receive Window (RWIN): 1034816 bytes
Selective ACKs: ON
Nagle Algorithm: ON
Explicit Congestion Notification: OFF
Time Stamping: OFF
Window Scaling: ON

------ Potential Bottlenecks ------
The theoretical network limit is 12.84 Mbps
The NDT server has a 2048.0 KByte buffer which limits the throughput to 139.82 Mbps
Your PC/Workstation has a 1010.0 KByte buffer which limits the throughput to 68.99 Mbps
The network based flow control limits the throughput to 28.96 Mbps

Client Data reports link is 'Ethernet', Client Acks report link is 'Ethernet'
Server Data reports link is 'T3', Server Acks report link is 'T3'

------ Routing Analysis ------
Information: Network firewall/router is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [96.28.53.213] but Client says [192.168.2.4]


Vista at Insight:
Your Download Speed = 20.16Mbps or 2.52MBytes/sec
Your Upload Speed = 1.38Mbps or 177.34KBytes/sec
Average round trip time = 32.23 ms


WEB100 Enabled Statistics:

------ Client System Details ------
OS data: Name = Windows Vista, Architecture = x86, Version = 6.0
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_21

------ Web100 Detailed Analysis ------
10 Mbps Ethernet link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found

Web100 reports the Round trip time = 32.23 msec; the Packet size = 1406 Bytes; and
There were 10 packets retransmitted, 247 duplicate acks received, and 247 SACK blocks received
The connection was idle 0 seconds (0%) of the time
This connection is receiver limited 32.19% of the time.
This connection is network limited 67.62% of the time.

The following TCP settings were detected:
TCP Receive Window (RWIN): 123648 bytes
Selective ACKs: ON
Nagle Algorithm: ON
Explicit Congestion Notification: OFF
Time Stamping: OFF
Window Scaling: ON

------ Potential Bottlenecks ------
The theoretical network limit is 22.82 Mbps
The NDT server has a 2048.0 KByte buffer which limits the throughput to 496.44 Mbps
Your PC/Workstation has a 120.0 KByte buffer which limits the throughput to 29.27 Mbps
The network based flow control limits the throughput to 45.26 Mbps

Client Data reports link is 'Ethernet', Client Acks report link is 'Ethernet'
Server Data reports link is 'T3', Server Acks report link is 'T3'

------ Routing Analysis ------
Information: Network firewall/router is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [96.28.53.213] but Client says [192.168.2.5]

Don't know where the 10 Mbps ethernet link is located or why Insight shows half duplex for the XP. Argonne Labs NDT shows full duplex.


Qwest Minneapolis Speedtest server shows
XP - Down 4.984 Mbps (0.6 MBps) UP 2.304 Mbps (0.2 MBps)
Latency 152ms

Vista - Down 21.59 Mbps (2.7 MBps) Up 1.382 Mbps (0.2 MBps)
Latency 32 ms

Any ideas?
User avatar
trogers
SG VIP
Posts: 12323
Joined: Wed Jan 26, 2005 11:14 pm
Location: Bangkok, Thailand

Post by trogers »

dlsayremn wrote:InsightBB 20/1.5 Mbps Service.

XP computer old Gateway Essential 667 upgraded from 98SE.
512 MB Ram
Wireless - Trendnet B/G TEW-423PI PCI Card (no ethernet)
Used TCP/IP Optimizer v. 3.0.3.0 with MTU of 1446.
Hardware and software seem to belong to the age when internet speed rarely exceed 8 Mbps.
"Contentment is not the fulfillment of what you want, but is the realisation of how much you already have" - anon
dlsayremn
Member
Posts: 85
Joined: Mon May 15, 2006 10:05 am
Location: Minneapolis, MN

Post by dlsayremn »

Hi, trogers. Yes it is old, like me. Still have the old Intel Internal 500 Kbps Modem for it.
User avatar
trogers
SG VIP
Posts: 12323
Joined: Wed Jan 26, 2005 11:14 pm
Location: Bangkok, Thailand

Post by trogers »

dlsayremn wrote:Hi, trogers. Yes it is old, like me. Still have the old Intel Internal 500 Kbps Modem for it.
I suspect the speed of the XP machine is limited by the old adapter card and its driver and is not designed to handle speed of up to 20 Mbps.

And even if you can get the speed up to 20 Mbps, the old comp's processor and graphic adapter may not be able to handle the heavily animated web pages or video feed.

Better if you get a more recent used comp to replace it.
"Contentment is not the fulfillment of what you want, but is the realisation of how much you already have" - anon
dlsayremn
Member
Posts: 85
Joined: Mon May 15, 2006 10:05 am
Location: Minneapolis, MN

Post by dlsayremn »

Using a two year old wireless card with drivers updated March 2010.

Seem to have improved speeds a little, but still get a lot a variability.

Went to j79zlr's cablenut calculator, Entered my MTU, down/up speeds, and let it calculate and setup parameters.

http://www.j79zlr.com/cablenutXP2k.php

Download: 20000kbps
Upload: 1500kbps
Latency: 100ms
MTU: 1446
DefaultReceiveWindow = 921600
DefaultSendWindow = 192000
DisableAddressSharing = 1
InitialLargeBufferCount = 200
InitialMediumBufferCount = 480
InitialSmallBufferCount = 640
LargeBufferSize = 819200
MaxFastTransmit = 64000
MediumBufferSize = 150400
Priority Boost = 0
SmallBufferSize = 12800
TransmitWorker = 32
FastSendDatagramThreshhold = 4096
EnableFastRouteLookup = 1
EnablePMTUDiscovery = 1
IgnorePushBitsOnReceives = 0
GlobalMaxTcpWindowSize = 250268
MaxFreeTcbs = 8000
MaxHashTableSize = 16384
MaxNormLookupMemory = 5000000
SackOpts = 1
SynAttackProtect = 1
Tcp1323Opts = 1
TcpLogLevel = 1
TcpMaxDupAttacks = 3
TcpMaxHalfOpen = 100
TcpMaxHalfOpenRetired = 80
TcpRecvSegmentSize = 1406
TcpSendSegmentSize = 1406
TcpTimedWaitDelay = 30
TcpUseRFC1122UrgentPointer = 0
TcpWindowSize = 250268
MaxConnectionsPer1_0Server = 20
MaxConnectionsPerServer = 10
DefaultTimeToLive = 64
DefaultUserTOSSetting = 0
TcpMaxDataRetransmissions = 6
DefaultTOSValue = 240

Used TCP/IP Optimizer to check various Receive Windows and picked best one.
« SpeedGuide.net TCP Analyzer Results »
Tested on: 09.08.2010 10:44
IP address: 96.28.xx.xxx
Client OS: Windows XP

TCP options string: 0204057e0103030301010402
MSS: 1406
MTU: 1446
TCP Window: 517408 (multiple of MSS)
RWIN Scaling: 3 bits (2^3=8)
Unscaled RWIN : 64676
Recommended RWINs: 64676, 129352, 258704, 517408, 1034816
BDP limit (200ms): 20696kbps (2587KBytes/s)
BDP limit (500ms): 8279kbps (1035KBytes/s)
MTU Discovery: OFF
TTL: 55
Timestamps: OFF
SACKs: ON
IP ToS: 11110000 (240)
Precedence: 111 (Network Control)
Delay: 1 (low delay)
Throughput: 0 (normal throughput)
Reliability: 0 (normal reliability)
Cost: 0 (normal cost)
Check bit: 0 (correct)
DSCP (DiffServ): No valid DiffServ equivalent (111100)


Speed Tests

NDT at Argonne National

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 1.41Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 19.35Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_21

------ Web100 Detailed Analysis ------
10 Mbps Ethernet 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 = 100.3 msec; the Packet size = 1406 Bytes; and
There were 1 packets retransmitted, 222 duplicate acks received, and 222 SACK blocks received
The connection was idle 0 seconds (0%) of the time
S2C throughput test: Packet queuing detected: 31.83%
This connection is receiver limited 6.99% of the time.
This connection is sender limited 54.1% of the time.
This connection is network limited 38.9% 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

Server 'ndt.anl.gov' is probably behind a firewall. [Connection to the ephemeral port failed]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [96.28.XX.XXX] but Client says [192.168.2.4]



Speedtest Net results:

Image

20 minutes later

Image

40 minutes later.

Image



Nitro.UCSC
TCP/Web100 Network Diagnostic Tool v5.5.4a
click START to begin

** Starting test 1 of 1 **
Connected to: nitro.ucsc.edu -- Using IPv4 address
Another client is currently being served, your test will begin within 90 seconds
Another client is currently being served, your test will begin within 45 seconds
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 1.39Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 16.30Mb/s
The slowest link in the end-to-end path is a 10 Mbps Ethernet subnet

NDT Servers are consistant, can't understand why Speedtest Net varies so much.
Post Reply