Amazing internets
I live well out in the country, you should check and see if there are any wireless carriers in your area. Basicly its a small sat dish pointed at a radio on a tower.
Yes, there is one. The dish is on a neighbor's roof. It's pretty expensive and I just really don't need it that badly. I have a pretty good dial up service and does all I really need. But, that is the only option as far as I know. The phone company does not offer anything because of the lines and there is no cable TV.
__________________
Jim
Jim
If this ran aa a TCP test, the speed would not be that high to your local Speedtest server ( at least not quite as fast with only 10ms round trip ).
With the delay from you to F150OL, you cannot get enough TCP packets in flight ( with default client settings ) to get those speeds.
That is one of the misconceptions of Speedtest.net. Most think they should be able to see those speeds to any server. Talking iPerf over a UDP session vs TCP session + application rendering.
You can try upping the TCP window size on your client to see if it helps. Thing is with a larger TCP window, if you loose even 1 packet, the fall back can be very painful to recover and ramp up again ( if slowstart is enabled ).
BrightHouse sucks butt! I pay for the upgrade speed and it's slow IMO. Their TV signal is even worse. I've had "pixelation" problems forever and nothing gets done. Paying 120 or so for phone, net and TV.
I want Verizon,,,that FIOS is the ****.
I want Verizon,,,that FIOS is the ****.
If I am not mistaken, Speedtest.net is running an iPerf of sorts ( this is the only way to figure true bandwidth speed, not application speed ).
If this ran aa a TCP test, the speed would not be that high to your local Speedtest server ( at least not quite as fast with only 10ms round trip ).
With the delay from you to F150OL, you cannot get enough TCP packets in flight ( with default client settings ) to get those speeds.
That is one of the misconceptions of Speedtest.net. Most think they should be able to see those speeds to any server. Talking iPerf over a UDP session vs TCP session + application rendering.
You can try upping the TCP window size on your client to see if it helps. Thing is with a larger TCP window, if you loose even 1 packet, the fall back can be very painful to recover and ramp up again ( if slowstart is enabled ).
If this ran aa a TCP test, the speed would not be that high to your local Speedtest server ( at least not quite as fast with only 10ms round trip ).
With the delay from you to F150OL, you cannot get enough TCP packets in flight ( with default client settings ) to get those speeds.
That is one of the misconceptions of Speedtest.net. Most think they should be able to see those speeds to any server. Talking iPerf over a UDP session vs TCP session + application rendering.
You can try upping the TCP window size on your client to see if it helps. Thing is with a larger TCP window, if you loose even 1 packet, the fall back can be very painful to recover and ramp up again ( if slowstart is enabled ).
...<snip>...As for the speeds to speedtest.net, it really doesn't matter who I test to. I always see 25-26 Mb/s. The reality is that I prolly will never click on any website that will give me their content at those speeds. I'm just happy to know that it's always fast, and I'm never the bottleneck.
Web sites use TCP, so there is an acknowledgment for x number of packets sent. The longer the delay, the longer it takes for the ack to come back, prior to sending more data. This is why the farther away a web site is ( time wise ) the slower it will act.
This does not mean you are not the bottle neck.
Unless the site is hosted by bob and joe's hosting company, they usually have either multiple Gig-E or 10Gig -E interfaces. This puts the sites bandwidth at 100X or more your bandwidth. That makes you the bottle neck as far as bandwidth total goes.
You will never see this problem on a web site, as with 10 ms with standard TCP window size, the best you will see is 51 Mbps of throughput.
40 ms of delay reduces it to 13 Mbps of throughput. This is with 0% packet loss, which is not the day in day out characteristic on the internet.
Unless you have more data in flight, you will never see the real performance of the faster VZ line.
You do have bragging rights to the fastest local loop line speed.
Compare your 26 Mbps line to a 15 Mbps line, both to a server that is 45 ms away, and both will act the same.



