Quote:
|
Another problem with sat Internet connections is latency. One packet has to travel about 48,000 miles and the acknowledgment does the same.
|
The latency isn't so much the distance traveled but the queue you wait in to use the satellite for data coming from the Internet to you. The stuff is going speed of light. No difference than emailing from my house to OZ.
The transmission starts with you and goes up then down to Ohio but when the response comes back they can only send one data stream to the satellite from the Network Operations Center in Ohio but it is a very high bandwidth signal using a really big dish with lots of power. What they do is your request for a file or web page to be sent to you gets split into many requests so they can in effect gather them quicker then send you bigger packages. Your package has to wait in line to be transmitted and that is where the latency comes in. I used it for a year and it's normally not that bad for web surfing. What is bad is the uploads from you to say an FTP site because the ACK that comes back to you when you send data has a longer latency than normal and it artificially makes the speed you can transmit a file lower than it really is because your target on the other side can't send the ACK's as fast as you could receive them. Your system has to wait for the ACK after each packet is send and with the latency delay it makes it seem dog slow. The bottom line is downloads are OK but uploads tend to suck.
The original Hughes satellite system used a telephone for the upstream side and the dish for download. DirecWay does it both ways. The really nice stuff called SpaceWay is higher bandwidth up and down but it's not cheap, and uses a bigger dish than even DirecWay. It's really meant for large companies out in the boonies.