Jump to content

tweaking


VanBuren

Recommended Posts

WEB100 Enabled Statistics:

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

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

running 10s inbound test (server to client) . . . . . . 5.03Mb/s

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

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

Java data: Vendor = Sun Microsystems Inc., Version = 1.4.2_05

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

10 Mbps Ethernet 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 = 130.26 msec; the Packet size = 1460 Bytes; and

There were 29 packets retransmitted, 228 duplicate acks received, and 130 SACK blocks received

The connection was idle 0 seconds (0%) of the time

This connection is network limited 99.97% of the time.

  Contact your local network administrator to report a network problem

  Contact your local network admin and report excessive packet reordering

    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 [69.169.215.xxx] but Client says [192.168.0.100]

i get better upload speesd to: http://miranda.ctd.anl.gov:7123/

WEB100 Enabled Statistics:

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

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

running 10s inbound test (server to client) . . . . . . 3.98Mb/s

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

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

Java data: Vendor = Sun Microsystems Inc., Version = 1.4.2_05

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

10 Mbps Ethernet link found.

Link set to Half 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 = 145.87 msec; the Packet size = 1380 Bytes; and

There were 46 packets retransmitted, 322 duplicate acks received, and 224 SACK blocks received

The connection was idle 0 seconds (0%) of the time

This connection is network limited 99.97% of the time.

  Contact your local network administrator to report a network problem

  Contact your local network admin and report excessive packet reordering

    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

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 [69.169.215.xxx] but Client says [192.168.0.100]

duplicate acks, no pl though. I think the duplicates may be my problem. If i crank up my send window, i get like 960 on the ndt tests, yet i cant go over around 70 KB/sec. Duplicate acks must slow it down.... so if i get it adjusted to where there aren't any dups, do you think it'll be faster?

Link to comment
Share on other sites

  • Replies 116
  • Created
  • Last Reply

Top Posters In This Topic

hmm... the anl test under more details says: (the 5mbit test)

estimate = 3.1 based on packet size = 10Kbits, RTT = 145.87msec, and loss = 5.41419E-4

The theoretical network limit is 3.1 Mbps

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

Your PC/Workstation has a 252.0 KByte buffer which limits the throughput to 13.49 Mbps

The network based flow control limits the throughput to 10.32 Mbps

Nitro gives me 3.08 dl and says:

estimate = 3.01 based on packet size = 11Kbits, RTT = 135.67msec, and loss = 7.45712E-4

The theoretical network limit is 3.01 Mbps

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

Your PC/Workstation has a 250.0 KByte buffer which limits the throughput to 14.44 Mbps

The network based flow control limits the throughput to 10.75 Mbps

Link to comment
Share on other sites

I have a fan blowing under my bed where the modem + linux firewall and my server are, as the modem + wireless router felt a little warm. I consistantly get 600 kbit upload (download needs to be retweaked i guess, 3-4 mbit) now that i have cool air blwoing on the stuff.... maybe it was too warm to do good or something.

Tracing route to testmy.net [67.19.36.6]

over a maximum of 30 hops:

  1    1 ms    1 ms    1 ms  smoothwall [192.168.0.1]

  2    28 ms    14 ms    14 ms  69.169.208.1

  3    15 ms    18 ms    11 ms  69.160.186.181

  4    19 ms    14 ms    20 ms  24.48.204.217

  5    14 ms    32 ms    19 ms  unk-426d0e99.adelphiacom.net [66.109.14.153]

  6    17 ms    35 ms    27 ms  p1-00-00-00.a0.cdp00.adelphiacom.net [66.109.1.4

6]

  7    26 ms    23 ms    37 ms  p3-02-00-00.r0.nyc90.adelphiacom.net [66.109.1.2

1]

  8    66 ms    62 ms    64 ms  p3-02-00-00.c1.chi75.adelphiacom.net [66.109.0.1

01]

  9    82 ms    82 ms    84 ms  p3-01-01-00.c1.dfw91.adelphiacom.net [66.109.0.6

6]

10    83 ms    91 ms    87 ms  g1-03-02-00.p0.dfw91.adelphiacom.net [66.109.3.7

8]

11    87 ms    94 ms    83 ms  eq-dallas-1000M.theplanet.com [206.223.118.3]

12    88 ms    84 ms    87 ms  dist-vlan31.dsr3-1.dllstx3.theplanet.com [70.85.

127.29]

13  124 ms  222 ms    76 ms  dist-vlan21.dsr1-1.dllstx2.theplanet.com [70.85.

127.67]

14    89 ms    78 ms    88 ms  dsr2-1-v1.dllstx4.theplanet.com [12.96.160.7]

15    95 ms    80 ms    87 ms  gig1-0-1.tp-car9-1.dllstx4.theplanet.com [67.18.

116.69]

16    81 ms    87 ms    88 ms  6.67-19-36.reverse.theplanet.com [67.19.36.6]

Trace complete.

Tracing route to miranda.ctd.anl.gov [146.137.222.101]

over a maximum of 30 hops:

  1    1 ms    1 ms    1 ms  smoothwall [192.168.0.1]

  2    26 ms    11 ms    23 ms  69.169.208.1

  3    18 ms    13 ms    21 ms  69.160.186.181

  4    52 ms    20 ms    16 ms  24.48.204.221

  5    37 ms    14 ms    23 ms  unk-426d0e99.adelphiacom.net [66.109.14.153]

  6    25 ms    24 ms    19 ms  p1-00-00-00.a0.cdp00.adelphiacom.net [66.109.1.4

6]

  7    32 ms    25 ms    34 ms  p3-02-00-00.r0.nyc90.adelphiacom.net [66.109.1.2

1]

  8    55 ms    70 ms    53 ms  p3-02-00-00.c1.chi75.adelphiacom.net [66.109.0.1

01]

  9    60 ms    59 ms    64 ms  a1-01-00-00.p0.chi75.adelphiacom.net [66.109.3.1

4]

10    62 ms    67 ms    59 ms  ge-6-2.car2.Chicago1.Level3.net [67.72.124.29]

11    53 ms    67 ms    63 ms  ae-1-52.bbr2.Chicago1.Level3.net [4.68.101.33]

12    82 ms    72 ms    75 ms  ae-0-0.bbr1.Washington1.Level3.net [64.159.0.229

]

13    88 ms    83 ms    75 ms  ge-1-1-51.car3.Washington1.Level3.net [4.68.121.

14]

14    80 ms    75 ms    70 ms  eqx-ash-level3.es.net [198.124.196.5]

15  141 ms  134 ms  133 ms  dccr1-eqx-ash.es.net [134.55.207.10]

16  130 ms  129 ms  140 ms  aoacr1-oc48-dccr1.es.net [134.55.209.61]

17  131 ms  138 ms  152 ms  chicr1-oc192-aoacr1.es.net [134.55.209.57]

18  136 ms  144 ms  131 ms  anl-oc12-chicr1.es.net [134.55.209.202]

19  138 ms  136 ms  132 ms  guava-esnet.anchor.anl.gov [192.5.170.77]

20  137 ms  128 ms  136 ms  130.202.222.65

21    *        *        *    Request timed out.

22    *    ^C

Tracing route to nitro.ucsc.edu [128.114.1.5]

over a maximum of 30 hops:

  1    1 ms    1 ms    1 ms  smoothwall [192.168.0.1]

  2    22 ms    11 ms    24 ms  69.169.208.1

  3    20 ms    45 ms    11 ms  69.160.186.181

  4    56 ms    12 ms    21 ms  24.48.204.217

  5    13 ms    19 ms    20 ms  unk-426d0e99.adelphiacom.net [66.109.14.153]

  6    27 ms    23 ms    12 ms  p1-00-00-00.a0.cdp00.adelphiacom.net [66.109.1.4

6]

  7    22 ms    22 ms    23 ms  p3-02-00-00.r0.nyc90.adelphiacom.net [66.109.1.2

1]

  8    24 ms    23 ms    29 ms  p3-00-01-00.c1.nyc90.adelphiacom.net [66.109.0.2

50]

  9    38 ms    31 ms    63 ms  p3-02-00-00.c0.dca91.adelphiacom.net [66.109.0.7

8]

10    87 ms    99 ms  138 ms  p3-01-00-00.c1.lax91.adelphiacom.net [66.109.0.2

01]

11  108 ms    91 ms    87 ms  p3-00-01-00.c0.lax91.adelphiacom.net [66.109.0.1

97]

12    93 ms  113 ms    96 ms  a1-00-00-00.p0.lax91.adelphiacom.net [66.109.3.1

30]

13    94 ms    99 ms    95 ms  lax-cenic-equinix-exch.cenic.org [206.223.123.7]

14  124 ms  115 ms  114 ms  dc-sac-dc1--lax-dc1-pos.cenic.net [137.164.22.12

7]

15  115 ms  151 ms  111 ms  dc-oak-dc2--csac-dc1-ge.cenic.net [137.164.22.11

0]

16  119 ms  116 ms  127 ms  ucsc-ucsc1--dc-oak-dc1-egm.cenic.net [137.164.23

.13]

17  119 ms  123 ms  119 ms  comm-g-GE3-5.ucsc.edu [128.114.0.214]

18  114 ms  119 ms  115 ms  nitro.ucsc.edu [128.114.1.5]

Trace complete.

Ping statistics for 128.114.1.5:

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

Approximate round trip times in milli-seconds:

    Minimum = 110ms, Maximum = 127ms, Average = 119ms

Control-C

thanks for the help so far.

Link to comment
Share on other sites

w/o load:

Ping statistics for 66.109.1.46:

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

Approximate round trip times in milli-seconds:

    Minimum = 11ms, Maximum = 89ms, Average = 26ms

w/ full download:

Ping statistics for 66.109.1.46:

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

Approximate round trip times in milli-seconds:

    Minimum = 11ms, Maximum = 83ms, Average = 39ms

Also that has an additional 5 KB/sec upload, as my mom picked up the phone in the middle of the loaded ping test

and QoS/traffic shaper is off.

Link to comment
Share on other sites

You know, i've been thinking. I read somewhere that the 2.3.1.3 firmware for the sb5100 was buggy. I think it was that. I have that same firmware.... some bug about uploading. Come to think of it, i got ~200kbit on my 256kbb cap, ~400 on my 512kb cap, and now ~600 on the 920 kb cap.... i posted on dslreports.com.

My laptops upload (which is wireless) is only slightly better. prolly not the nic, aren't intel nics good?

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...