Re: Went from 116kps to 1.8 mps with TCPOptimzer??
Gimpy00Wang, I hope you're not calling me an intelligent fellow /ubbthreads/images/graemlins/wink.gif But I'll back you up.
You can't increase the speed of your connection. But it MAY be doing things to change how you're using it. Packet size is one thing that can be adjusted, but I don't think that can affect incoming data, which may be in any size, but rather outgoing when you're making your own packets. I can't back that up, but it's my suspicion.
The other thing I've seen done is similar to what those 2 way satelight links do. There is a lot of error checking in TCP, thats how it works as a "guaranteed" relayer of data. Basically when I open a connection I'm promised by the system to either get the data, or get an error, but I'll never have bits missing or screwed up data. This means sending a lot of info back and forth, it's not just a stream of data, but acks and replies and such need to go back and forth. So you can only download as fast as you can send acks for the packets back to the server. Since the latency is SO bad on satelight systems they basically turn this off and just pump data down as fast as they can and rely on your computer to keep up. This works pretty good for web browsing but for other things it can definitely increase errors and make corrupt data.
They could be doing something like that. Actually MS does this kind of thing all the time. It's built into IE and IIS, if they are talking to each other IIS doesn't wait for the ack packets and just dumps the data at you. This is why some sites load almost instantly in IE and others seem to take a long time to start downloading. Cause IE has to realize that the first request didn't work and then do it over properly.
But, in order to make any difference that requires that both sides of the conversation are aware of the broken protocol. It won't make a difference to a regular connection between regular machines.
So the bottom line is that i've written this entire email without a clue as to what is happening or why it seems like you're getting faster data.
Bigger packets mean fewer acks need to go back and forth, so it can increase the perceived throughput, but not by nearly that much. And it would create slower connections for anything else that was happening over the network as it wouldn't share as nicely with other connections.
So run those tests over at dslreport.com and let us know what happens!