Hey maxwarp!
you are lucky
here setting the same values to my stack IP i have no iprovements at all
still 500-600KiloBytes download from Firefox or from wget at the command prompt on my eCS2.1 desktop with an Intel pro 1000 XT PCI-X Nic… binded at gigabit ethernet to my Cisco gigabit ethernet switch
that communicate with my Cisco 8xx router that runs an FTTC 100Mb/sec….
...
guys, any help?
...
Yeah, I feel your pain...when it comes to on-line "feel" nothing beats a fast connection speed and when it's not there it gets pretty frustrating.
OK, so a couple of things:
1) various test servers will be impacted by your local tcpip stack settings, for example, take the SACK flag...as I mentioned in my response to Roderick, I did shut it off right now to test it out, the immediate impact => speedtest.net DIES!!! I get a burst of full speed for about 2-3 secs then the traffic completely stops...judging by this result alone I would be inclined to say that having SACK OFF is a mistake...yet hitting several of the other test servers shows no impact, so your results will vary
2) this is a bit of a follow-up to the idea above, but as applicable to the bigger internet picture...you will get different speeds from different servers, so just because I can do 10 Mbyte to my local test server (same city actually) it does not mean that a server somewhere in China or EU for that matter will show the same results...network latency adds up, etc, etc
3) now to be more specific, can you test what you are seeing using another machine on your LAN? For example, in my testing I was attempting to debug the OS/2 issue but my other boxes (Win7 and mobile devices) were showing decent results...is that the case for you as well? If yes, then indeed, the problem appears to lie with the OS/2 setup itself, if no, then it may very well exist outside of your LAN and on the WAN side
4) there are some more in-depth tools you could use, take a look at the port of Wireshark (
https://os2ports.smedley.id.au/index.php?page=wireshark) that Paul Smedley did, it will allow you to visually inspect your tcpip stack traffic and may highlight where your OS/2 specific configuration issue lies, great tunning aid, a bit of a learning curve, you need to capture a tcpip trace on your OS/2 machine then pull this into the Wireshark app, not complex at all, but if you're never done it you just have to try it out a couple of times (look up the thread we had on this forum regarding this, great discussion), heck, that could be a great general discussion of how to tune the OS/2 tcpip stack and maybe deserves a separate thread?