now for the tweaking....
first the background....
you are connected to a telco that has a card located in a kit called dslam.
from there, the telco handles your data traffic and passes it to your isp's servers or routers....
all the action is maintained by the telco...so the telco's data handling info is important to you...
your isp will set your kb rate or top speed.....they implement the throttles basically and such stuff......
one of these piece of info is the mtu or maximum transmision unit....
its the size of the packet before its broken into more than one piece....
if you are playing a game, you dont want small pieces of info being broken into two...you want it in one for response...like that left turn you buss on an opponent to zap him...![]()
now most telco's will have an mtu of around 1500 max but here in the uk we found by testing that it was more like 1450...and it took a while before BT admitted it was 1458..
most routers you buy comes with 1500 as default...also, i think windows does the same.....by experimenting with your mtu, you can find the best for you.....
we'll discuss how at the end.
*the best dialup mtu is 576.......
next thing is the TCP recieve window....this is the actual data your comp is willing to handle as one data packet so to speak.....
think of it as a block of info you are going to recieve...
this is similar to your mtu in that your comp will address that data in one go and the size of it is what will be addressed....
the bigger it is, the better for downloading until you reach a critical point and then it becomes two blocks...and the usual happens with breaking up and waiting...
the smaller it is is better for gaming....you dont want big info to get to you and you have to wait before your screen gets updated.....see me?
its another one for experimenting with.....
there are some general default reccomendation, which i will find for ya, but for now we are going through how this stuff actually works and how you yourself can optimise your own comp....
next one is the time to live or TTL as its known.....this is the one where you send and how long you should wait for a reply or acknowledge from the other end.....
there is also an ACK setting which is basically how many ack should you wait for before iving up totally....
i set mine at 128 in agreement with other people i know but others have claimed good results at other values...
now the tool to use for the above stuff is dr.tcp....this is a windows tool.....im sure that there is a way that the linux buds can set these things but im not familiar with them to be honest....
but all that wont matter with the page that i direct you to....it can handle all as its using java....
the tweak page will suggest values from which you can start....
for all users...the following is important...
use this tweak test page to first determine your what you settings should be.....its a good place to start tweaking from......
http://www.dslreports.com/tweaks
continued......