Newbie here, Looking for help with TCP Optimizer settings.....

[Brickman45]

New here.

Trying to get all my settings right in TCP Optimizer.
Not sure if I can copy over all my testing results yet, if so please let me know.

Not real good at typing or computer use yet, I am learning as quick as I can.
Have been getting conflicting advice on settings of TCP Optimizer and Network adapter settings.

So today I have used the preset Optimal setting for TCP Optimizer rather than my custom settings.
Not sure if I am interpreting the results of the TCP Analyzer.

Would appreciate any help concerning these results and settings.

And a Big Hello to all the community here, I have every intention of becoming a Cyber/Guru/Brainiack.

[Philip]

Hello, and welcome to SG

The TCP Optimizer "optimal" settings are what usually works for the majority of users to make a few tweaks that help improve broadband internet connections. From there on, there are some minor changes you can make if you're more game oriented, etc. but you will likely not see noticeable difference. The documentation can help with all the settings: https://www.speedguide.net/articles/...8-10-2012-5821

The Analyzer just shows what settings are displayed on the other end of connections when your client connects. It reads the TCP/IP headers and displays the results.

If you have question about specific Optimizer settings please just ask, the Analyzer has a "share your results" section at the bottom of the page if you want.

[Brickman45]

Hey, thanks.
Yes, that's what I ended up doing. Right now, I'm on Edge Browser, am usually on Firefox.
Love this site. Just did a fresh install 10 days ago, and am spending all day and nights learning, there is no end to it.

Good thing though is I love this stuff. So far, it seems everything is pretty solid and responsive. I imagine I will always be trying to Tweak everything. Alot of new concepts and terminology to learn.
My speed test tonight using Edge Browser is weird though, Browser feels very snappy and super quick, but that Ping and Jitter are nuts.
I'm not really good yet at all this typing and operating system usage, but I will endeavor to figure out how to post stuff in these forums so I can access the help I seek.

[Brickman45]

« SpeedGuide.net TCP Analyzer Results »
Tested on: 2022.10.24 00:12
IP address: 47.36.xxx.xxx
Client OS/browser: Windows 10 (Firefox 106.0)

TCP options string: 020405b4010303080402080a00d9687100000000
MSS: 1460
MTU: 1500
TCP Window: 263424 (not multiple of MSS)
RWIN Scaling: 8 bits (2^8=256)
Unscaled RWIN : 1029
Recommended RWINs: 64240, 128480, 256960, 513920, 1027840
BDP limit (200ms): 1054 Mbps (105 Megabytes/s)
BDP limit (500ms): 421 Mbps (42 Megabytes/s)
MTU Discovery: ON
TTL: 48
Timestamps: ON
SACKs: ON
IP ToS: 00000000 (0)

[Brickman45]

« SpeedGuide.net Speed Test Results »
321.48 Mbit/s down ↓
10.09 Mbit/s up ↑
ping: 24ms jitter: 1ms

Test date: 2022.10.23 03:46 EDT
IP Address: 47.36.xxx.xxx
Location: Klamath Falls, OR, US
Provider: res.spectrum.com

mirror: backyardengineering.com (Fremont, CA USA)
Test Link: https://www.speedguide.net/speedtest...est=1666511182

[Brickman45]

Pinging [68.67.73.20] with 32 bytes ->bytes=32 time=120ms TTL=45
Pinging [68.67.73.20] with 32 bytes ->bytes=32 time=110ms TTL=45
Pinging [68.67.73.20] with 32 bytes ->bytes=32 time=111ms TTL=45
Pinging [109.105.110.44] with 32 bytes ->bytes=32 time=193ms TTL=45
Pinging [109.105.110.44] with 32 bytes ->bytes=32 time=193ms TTL=45
Pinging [109.105.110.44] with 32 bytes ->bytes=32 time=191ms TTL=45
Pinging [104.247.81.71] with 32 bytes ->bytes=32 time=171ms TTL=43
Pinging [104.247.81.71] with 32 bytes ->bytes=32 time=130ms TTL=43
Pinging [104.247.81.71] with 32 bytes ->bytes=32 time=103ms TTL=43
Pinging [142.250.188.228] with 32 bytes ->bytes=32 time=41ms TTL=112
Pinging [142.250.188.228] with 32 bytes ->bytes=32 time=40ms TTL=112
Pinging [142.250.188.228] with 32 bytes ->bytes=32 time=38ms TTL=112
Pinging [34.209.167.56] with 32 bytes ->Request Timed Out
Pinging [34.209.167.56] with 32 bytes ->Request Timed Out
Pinging [34.209.167.56] with 32 bytes ->Request Timed Out
Pinging [23.14.168.237] with 32 bytes ->bytes=32 time=21ms TTL=55
Pinging [23.14.168.237] with 32 bytes ->bytes=32 time=24ms TTL=55
Pinging [23.14.168.237] with 32 bytes ->bytes=32 time=20ms TTL=55
Pinging [98.137.11.164] with 32 bytes ->bytes=32 time=28ms TTL=51
Pinging [98.137.11.164] with 32 bytes ->bytes=32 time=24ms TTL=51
Pinging [98.137.11.164] with 32 bytes ->bytes=32 time=25ms TTL=51
Ping statistics for above hosts:
Packets: Sent = 21, Received = 18, Lost = 3 (14% loss)
Approximate round trip times (RTT) in milli-seconds:
Minimum = 20ms, Maximum = 193ms, Average = 75ms

[Philip]

Thanks for the good words about the site, plenty of info in the Articles section can help you with all those tweaks.

Everything seems fine with your connection at first glance, latency to the East Coast is a bit higher, West Coast is good. The Ookla speedtest.net may be even better than ours for testing your speed, they have more speed test mirrors.

Newer Windows versions are getting better at utilizing the potential of broadband internet connections by default, after using the "optimal" settings of the TCP Optimizer you have covered most basic tweaks. If you want you can look over your Network Adapter settings and turn off any "coalescing", power saving features, and most "offload" settings, except maybe "checksum offloads".

There is more info on those Network Adapter settings here, if interested: https://www.speedguide.net/articles/...imization-3449
If you're using Wi-Fi there is a wireless version as well: https://www.speedguide.net/articles/...ed-tweaks-5681

[Brickman45]

Pretty good results today, Here is latest run...

« SpeedGuide.net TCP Analyzer Results »
Tested on: 2022.10.25 20:27
IP address: 47.36.xxx.xxx
Client OS/browser: Windows 10 (Firefox 106.0)

TCP options string: 020405b4010303080402080a000990b500000000
MSS: 1460
MTU: 1500
TCP Window: 263424 (not multiple of MSS)
RWIN Scaling: 8 bits (2^8=256)
Unscaled RWIN : 1029
Recommended RWINs: 64240, 128480, 256960, 513920, 1027840
BDP limit (200ms): 1054 Mbps (105 Megabytes/s)
BDP limit (500ms): 421 Mbps (42 Megabytes/s)
MTU Discovery: ON
TTL: 48
Timestamps: ON
SACKs: ON
IP ToS: 00000000 (0)

[Brickman45]

« SpeedGuide.net TCP Analyzer Results »
Tested on: 2022.11.02 15:15
IP address: 131.150.xx.xxx
Client OS/browser: Windows 10 (Firefox 106.0)

TCP options string: 020405b40103030e01010402
MSS: 1460
MTU: 1500
TCP Window: 262144 (not multiple of MSS)
RWIN Scaling: 14 bits (2^14=16384)
Unscaled RWIN : 16
Recommended RWINs: 64240, 128480, 256960, 513920, 1027840
BDP limit (200ms): 1049 Mbps (105 Megabytes/s)
BDP limit (500ms): 419 Mbps (42 Megabytes/s)
MTU Discovery: ON
TTL: 49
Timestamps: OFF
SACKs: ON
IP ToS: 00000010 (2)
Precedence: 000 (routine)
Delay: 0 (normal delay)
Throughput: 0 (normal throughput)
Reliability: 0 (normal reliability)
Cost: 1 (low cost)
Check bit: 0 (correct)
DSCP (DiffServ): CS0 000000 (0) - class 0, default traffic (RFC 2474).

[Philip]

You don't need to post every result, the maximum theoretical throughput is just calculated for a certain latency as a guideline, it is not intended as a speed test.

What I did notice in your last post is that it lets you set the IP ToS field, that's cool...
https://www.speedguide.net/articles/...-dscp-wmm-3477