I did a connection speed test at <http://jlab4.jlab.org:7123/>, and received the advice that: "Increasing the current receive buffer (63.0 KB) will improve performance." The detailed results are included below.
My question is how may I increase the "current receive buffer," and/or is it something I should not do.
Enver
----------------------
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 350.98Kb/s
running 10s inbound test (server to client) . . . . . . 1.48Mb/s
------ Client System Details ------
OS data: Name = Mac OS X, Architecture = ppc, Version = 10.3.9
Java data: Vendor = Apple Computer, Inc., Version = 1.4.2_05
------ 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 = 331.37 msec; the Packet size = 1368 Bytes; and
No packet loss - but packets arrived out-of-order 0.14% of the time
This connection is receiver limited 92.01% of the time.
Increasing the current receive buffer (63.0 KB) will improve performance
This connection is network limited 7.83% of the time.
Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: OFF
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: ON
RFC 1323 Window Scaling: OFF
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 [70.17.114.192] but Client says [10.0.1.2]
My question is how may I increase the "current receive buffer," and/or is it something I should not do.
Enver
----------------------
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 350.98Kb/s
running 10s inbound test (server to client) . . . . . . 1.48Mb/s
------ Client System Details ------
OS data: Name = Mac OS X, Architecture = ppc, Version = 10.3.9
Java data: Vendor = Apple Computer, Inc., Version = 1.4.2_05
------ 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 = 331.37 msec; the Packet size = 1368 Bytes; and
No packet loss - but packets arrived out-of-order 0.14% of the time
This connection is receiver limited 92.01% of the time.
Increasing the current receive buffer (63.0 KB) will improve performance
This connection is network limited 7.83% of the time.
Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: OFF
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: ON
RFC 1323 Window Scaling: OFF
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 [70.17.114.192] but Client says [10.0.1.2]
