SG Broadband Community

is that lan request buffer size of TCP and the AFD buffer of cablenut is same??

No. LAN request buffer size of TCP Optimizer is the same as MaxHashTableSize of Cablenut.

AFD parameters of Cablenut, DefaultReceiveWindow and DefaultSendWindow, are not tweaked in TCP Optimizer. They are not TCP settings but are settings for internal file handing of the OS.

If your OS is XP SP2, you should leave a blank for DefaultReceiveWindow as any value entered into this field will override TCP Window for this OS.

how do you compute the Rwin do you have a own formula? because in optimal settings the Rwin of 384 kbps is 24820 then plus 1460 = 26280 and that was the Rwin you gave me? ^^

i89WipeR wrote:how do you compute the Rwin do you have a own formula? because in optimal settings the Rwin of 384 kbps is 24820 then plus 1460 = 26280 and that was the Rwin you gave me? ^^

The appropriate Rwin value follows the following Bandwidth Delay Product (BDP) formula:

RWIN = Bandwidth x Max. Latency divided by 8

Also, we choose a Rwin value that is an even multiple of MSS.

The trick in using the above formula is in selecting the correct value for Max. Latency.

I usually use 500ms for max. latency for users in Asean to the US.

So, bandwidth = 384 kbps and max.latency = 500

Rwin = 384 x 500 / 8 = 24000

Next we divided Rwin with MSS = 24000 / 1460 = 16.43

You can choose to use Rwin = 1460 x 16 = 23360 or 1460 x 18 = 26280. The former gives you a max. latency below 500ms and the latter above 500ms.

Rwin = 24820 is an odd multiple of MSS = 1460 x 17

how about the lan request buffer size how can you get the 32768? and in defautTOSvalue can i use 184?

i89WipeR wrote:how about the lan request buffer size how can you get the 32768? and in defautTOSvalue can i use 184?

LAN request buffer does nothing to your internet connection speed. It is a buffer for data transfer between comps in a LAN. Both Cablenut and TCP Optimizer recommend it set to 16384. We choose to double this value in view of higher RAM being used in comps these days.

ToS set to 184 is not recommended as you will encounter packet losses. See below:

# DefaultTOSValue = 184 - (101 110 00 binary). This is a very aggressive setting, that might introduce some packet loss - it is usually only recommended for audio/video applications. For ToS, you get critical precedence, low delay, high throughput. For DiffServ, you get EF - Expedited Forwarding, high priority traffic, but with higher drop probability.

I usually recommend trying 80,96,104,128 and 136.

is that MaxHashTablesize and Lan request buffer size are same? because they have same optimal value..16384

i89WipeR wrote:is that MaxHashTablesize and Lan request buffer size are same? because they have same optimal value..16384

You can manually change the value of this registry entry and see if there is a similar change to Cablenut display of values:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

my settings are fully tweak but ..

i89WipeR wrote:
my settings are fully tweak but ..

Could be a problem somewhere along your signal route to the test server. Your latency is over 900ms to Quezon city. Try testing at some other test server.

ah..ok in defaultTOSvalue you give me 80 can i use 240?

i89WipeR wrote:ah..ok in defaultTOSvalue you give me 80 can i use 240?

What I gave earlier are for Diff Serv values that have equivalent in ToS. You can try 92 and 240 as ToS values, but they will not have equivalent in Diff Serv.

my ISP give me 384kbps is this good?

i89WipeR wrote:

my ISP give me 384kbps is this good?

Very good. In tweaking, we aim to get about 90%. You achieved 98%. But do note that our speed can fluctuate at different times of the day, and slowdown would be expected during peak traffic hours - usually 4-11pm.

how to compute my tweak achieve?

i89WipeR wrote:how to compute my tweak achieve?

Speed tested divided by ISP given speed = 380/384 = 98%

our goal si 90% what is the meaning if below 90%?

i89WipeR wrote:our goal si 90% what is the meaning if below 90%?

That depends on how much below. If it is within 80-90%, the slightly lower speed may be due to interference noise in the line which cannot be corrected by users, but may need a major rewiring job.

If it is much below 80%, then problem could be with a bad line, or signal hardware, or interference over the wireless connection, or bad software or insufficient processing speed or memory.

Troubleshooting will take time and possible source of the problem has to be eliminated one at a time to identify the real cause.

my internet speed is 384 is this kilobytes or kilobbits?

i89WipeR wrote:my internet speed is 384 is this kilobytes or kilobbits?

All ISPs advertise speed in kilobits per second (kbps) or megabits per second (mbps). Do we not all wish it was Kilo Bytes per second (KB/s)?

in TCPoptimizer there was a tab called LATENCY..hmm the latency here to me is range to 400-500ms(MAXIMUM) in SPEEDTEST.NET is 999ms ..what do you think??

i89WipeR wrote:in TCPoptimizer there was a tab called LATENCY..hmm the latency here to me is range to 400-500ms(MAXIMUM) in SPEEDTEST.NET is 999ms ..what do you think??

As the test server is less then 100km from you, I would suspect your signals are encountering some problematic intermediate router along the path to the test server.

But I base Max Latency on "Round Trip Time" to a NDT test site in mid-US. This is a more accurate measure for latency as I surf to the US often.

You can do the same test at this link. Click the 'Statistics' button after the test is completed and find your round trip time (RTT):

http://miranda.ctd.anl.gov:7123/

ah.ok one last why do we need our RWIN to be a multiple of mss?

i89WipeR wrote:ah.ok one last why do we need our RWIN to be a multiple of mss?

RWIN is the value that sets the TCP buffer which stores pure data packets (MSS). When the buffer is full, the comp sends out a receipt acknowledgement to the sending comp. To optimize, this buffer should store whole data packets without any unfilled space, thus its size should be a multiple of MSS.

my connection in 3:30am