Need help optimizing verizon/moto q tether speeds.

mmync

Hello all, glad to find this great forum and nice to meet you all. I have done a ton of reading over the last couple of months but cant seem to be able to get anywhere on my own so I decided to ask for some help. I dont feel like I am getting the speeds that I should be getting and am sure there are alot of things that I dont have configured properly to get decent and consistent speeds. I am willing to do any tests to supply the necessary information to get this all tuned up. I am located it St. Clair Shores, Michigan (Zip here is 48081). I am using a Motorola Q and I am on the unlimited pda plan. I hook up via usb to my laptop which is currently running vista. I would not have a problem switching to XP if it would help. I tether inside my house and dont get the greatest signal which probably has alot to do with it. I usually only have only 1 or 2 bars of signal strength while inside my house. I am willing to get an external antenna if that will help at all. Thanks in advance and sorry if I havent provided all the necesarry information

mmync · Posted: Sat Apr 14, 2007 1:21 pm Post subject:

Ok I just did a master reset so we can start fresh. Yes I do have evdo although I am only getting like 1 bar on my phone. Here are some test results. I ran these first 3 directly on my phone from dslreports mobile speed test at 12:00 pm and used the 600k download. 1st test (108k/latency=.928) 2nd test (128k/latency=.561) 3rd test (259k/latency=.546)

Here is a speedtest.net test on my laptop via usb tether at 12:45pm

« SpeedGuide.net TCP Analyzer Results »
Tested on: 04.14.2007 12:49
IP address: 70.217.xxx.xxx

TCP options string: 020405b401010402
MSS: 1460
MTU: 1500
TCP Window: 17520 (multiple of MSS)
RWIN Scaling: 0
Unscaled RWIN : 17520
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 701kbps (88KBytes/s)
BDP limit (500ms): 280kbps (35KBytes/s)
MTU Discovery: ON
TTL: 109
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)

And finally the Argonne NDT server test.

« SpeedGuide.net TCP Analyzer Results »
Tested on: 04.14.2007 12:49
IP address: 70.217.xxx.xxx

TCP options string: 020405b401010402
MSS: 1460
MTU: 1500
TCP Window: 17520 (multiple of MSS)
RWIN Scaling: 0
Unscaled RWIN : 17520
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 701kbps (88KBytes/s)
BDP limit (500ms): 280kbps (35KBytes/s)
MTU Discovery: ON
TTL: 109
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 83.38Kb/s
running 10s inbound test (server to client) . . . . . . 318.99kb/s

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

------ 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 = 347.62 msec; the Packet size = 1460 Bytes; and
There were 3 packets retransmitted, 12 duplicate acks received, and 13 SACK blocks received
The connection stalled 1 times due to packet loss
The connection was idle 0.58 seconds (5.8%) of the time
This connection is receiver limited 32.76% of the time.
Increasing the the client's receive buffer (25.0 KB) will improve performance
This connection is network limited 67.2% 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: OFF
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End

WEB100 Kernel Variables:
Client: localhost/127.0.0.1
AckPktsIn: 144
AckPktsOut: 0
BytesRetrans: 4380
CongAvoid: 70
CongestionOverCount: 0
CongestionSignals: 1
CountRTT: 130
CurCwnd: 21900
CurMSS: 1460
CurRTO: 580
CurRwinRcvd: 20440
CurRwinSent: 5840
CurSsthresh: 11680
DSACKDups: 0
DataBytesIn: 0
DataBytesOut: 413180
DataPktsIn: 0
DataPktsOut: 283
DupAcksIn: 12
ECNEnabled: 0
FastRetran: 0
MaxCwnd: 26280
MaxMSS: 1460
MaxRTO: 1370
MaxRTT: 660
MaxRwinRcvd: 26280
MaxRwinSent: 5840
MaxSsthresh: 11680
MinMSS: 1460
MinRTO: 580
MinRTT: 240
MinRwinRcvd: 17520
MinRwinSent: 5840
NagleEnabled: 1
OtherReductions: 1
PktsIn: 144
PktsOut: 283
PktsRetrans: 3
X_Rcvbuf: 107520
RcvWinScale: 2147483647
SACKEnabled: 3
SACKsRcvd: 13
SendStall: 0
SlowStart: 24
SampleRTT: 340
SmoothedRTT: 330
X_Sndbuf: 107520
SndWinScale: 2147483647
SndLimTimeRwin: 3390447
SndLimTimeCwnd: 6953080
SndLimTimeSender: 3053
SndLimTransRwin: 5
SndLimTransCwnd: 5
SndLimTransSender: 1
SndLimBytesRwin: 110960
SndLimBytesCwnd: 302220
SndLimBytesSender: 0
SubsequentTimeouts: 0
SumRTT: 45190
Timeouts: 1
TimestampsEnabled: 0
WinScaleRcvd: 2147483647
WinScaleSent: 2147483647
DupAcksOut: 0
StartTimeUsec: 555635
Duration: 10348611
c2sData: 2
c2sAck: 2
s2cData: 9
s2cAck: 2
half_duplex: 0
link: 100
congestion: 0
bad_cable: 0
mismatch: 0
spd: 0.00
bw: 0.54
loss: 0.003533569
avgrtt: 347.62
waitsec: 0.58
timesec: 10.00
order: 0.0833
rwintime: 0.3277
sendtime: 0.0003
cwndtime: 0.6720
rwin: 0.2005
swin: 0.8203
cwin: 0.2005
rttsec: 0.347615
Sndbuf: 107520
aspd: 0.00000

Checking for mismatch on uplink
(speed > 50 [0>50], (xmitspeed < 5) [0.08<5]
(rwintime > .9) [0.32>.9], (loss < .01) [0.00<.01]
Checking for excessive errors condition
(loss/sec > .15) [3.53>.15], (cwndtime > .6) [0.67>.6],
(loss < .01) [0.00<.01], (MaxSsthresh > 0) [11680>0]
Checking for 10 Mbps link
(speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]
(xmitspeed < 9.5) [0.08<9.5] (loss < .01) [0.00<.01], (mylink > 0) [3.0>0]
Checking for Wireless link
(sendtime = 0) [3.0E=0], (speed < 5) [0<5]
(Estimate > 50 [0.54>50], (Rwintime > 90) [0.32>.90]
(RwinTrans/CwndTrans = 1) [5/5=1], (mylink > 0) [3.0>0]
Checking for DSL/Cable Modem link
(speed < 2) [0<2], (SndLimTransSender = 0) [1=0]
(SendTime = 0) [3.0E-4=0], (mylink > 0) [3.0>0]
Checking for half-duplex condition
(rwintime > .95) [0.32>.95], (RwinTrans/sec > 30) [0.5>30],
(SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]
Checking for congestion
(cwndtime > .02) [0.67>.02], (mismatch = 0) [0=0]
(MaxSsthresh > 0) [11680>0]

estimate = 0.54 based on packet size = 11Kbits, RTT = 347.62msec, and loss = 0.003533569
The theoretical network limit is 0.54 Mbps
The NDT server has a 105.0 KByte buffer which limits the throughput to 2.35 Mbps
Your PC/Workstation has a 25.0 KByte buffer which limits the throughput to 0.57 Mbps
The network based flow control limits the throughput to 0.57 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'

chong67 · EVDO Fledgling Joined: 12 Jun 2006 Posts: 23

Thats about the same speed here in Atlanta if I sit near a window.

LIVE4SPD · Posted: Thu Jun 28, 2007 1:57 pm Post subject:

Did you do the registry tweaks on your Q for the Max Connections and Max Threads?

*************

One of the most common and effective tweaks for web browsers on the desktop is also possible for IE on WM5. Stored in the registry are two keys which tell Internet Explorer how many connections it should make to a server when downloading a web page. They define the "Maximum number of concurrent connections" and they're just itching for a tune-up.

By [Creating] the following [DWord] key:

HKCU/Software/Microsoft/Internet Explorer/Main/MaxRequestThreads = 25

to a value higher than the default (5) will enable greater bandwidth saturation during page download and a noticable improvement in page load time. I took a guess and raised the MaxThreads to 10 and have had no problems (thus far).

[Update] Also, you will want to add the dword value:

HKCU/Software/Microsoft/Internet Explorer/Main/MaxConnectionsPerServer = 25