GunZ Factor Forums

Go Back   GunZ Factor Forums > GunZFactor Forums > The Garrison

Become a Gold or Silver Member

Reply
 
Thread Tools
Old 07-10-2008, 09:35 PM   #31 (permalink)
Gunzfactorian Hero
 
semiiee's Avatar
 

Join Date: Oct 2007
Location: Secret Azure Hideout
Posts: 3,234
semiiee has a reputation beyond repute.semiiee has a reputation beyond repute.semiiee has a reputation beyond repute.semiiee has a reputation beyond repute.semiiee has a reputation beyond repute.semiiee has a reputation beyond repute.semiiee has a reputation beyond repute.semiiee has a reputation beyond repute.semiiee has a reputation beyond repute.
Default Re: Things you don't know about lag, and how to fix them.

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

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

------ 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 = 197.74 msec; the Packet size = 1460 Bytes; and
There were 5 packets retransmitted, 51 duplicate acks received, and 63 SACK blocks received
The connection was idle 0 seconds (0%) of the time
C2S throughput test: Packet queuing detected: 3.63%
S2C throughput test: Packet queuing detected: 11.07%
This connection is receiver limited 12.03% of the time.
Increasing the the client's receive buffer (17.0 KB) will improve performance
This connection is network limited 87.88% 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

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End





iz bad?
__________________

semie

semiiee is offline   Reply With Quote
Old 11-18-2008, 09:31 AM   #32 (permalink)
Member
 

Join Date: Jan 2007
Posts: 35
skyblade15 is on a distinguished road.

Default Re: Things you don't know about lag, and how to fix them.

where is the start button on the webpage ?
skyblade15 is offline   Reply With Quote
Old 11-30-2008, 02:58 PM   #33 (permalink)
Member
 

Join Date: May 2007
Posts: 11
angel_115 is dishonorable.

Default Re: Things you don't know about lag, and how to fix them.

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

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

------ 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 = 489.64 msec; the Packet size = 1460 Bytes; and
No packet loss - but packets arrived out-of-order 17.61% of the time
C2S throughput test: Packet queuing detected: 6.25%
S2C throughput test: Packet queuing detected: 7.28%
This connection is receiver limited 78.69% of the time.
Increasing the the client's receive buffer (62.0 KB) will improve performance
This connection is network limited 21.15% 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

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is not behind a firewall. [Connection to the ephemeral port was successful]
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End
angel_115 is offline   Reply With Quote
Old 11-30-2008, 04:12 PM   #34 (permalink)
Gunzfactorian
 
BeyondStrike's Avatar
 

Join Date: Oct 2008
Posts: 151
BeyondStrike has chosen the path of honor.

Default Re: Things you don't know about lag, and how to fix them.

Connected to: nitro.ucsc.edu -- Using IPv4 address
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 117.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 772.23kb/s
Your PC is connected to a Cable/DSL modem
Information: Other network traffic is congesting the link
BeyondStrike is offline   Reply With Quote
Reply

Tags
…noob was here., ham, slap_lags

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


All times are GMT -5. The time now is 09:23 AM.


Powered by vBulletin®
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34