low-latency bandwidth for cheap?
This may be the wrong forum to ask this, and if so I apologize, please just point me in the right direction! I'm getting somewhat frustrated with the instability and high latency of residential cable and DSL offerings, but I love the T1 or greater bandwidth they offer. I'd like reasonable bandwidth with low latency without spending hundreds of dollars per month! Anybody know a good source for near-T1 low-latency bandwidth at around $100/month? I'm in the northern VA area btw. -- Jeff Wheeler Postmaster, Network Admin US Institute of Peace
On Wed, 04 Aug 2004 17:25:43 EDT, Jeff Wheeler writes:
I'm getting somewhat frustrated with the instability and high latency of residential cable and DSL offerings, but I love the T1 or greater bandwidth they offer. I'd like reasonable bandwidth with low latency without spending hundreds of dollars per month!
RFC 1925, 7a. cheers, &rw -- -- Dawn is nature's way of telling you to go to bed. -- -> And to just stay there until the evil yellow -- disk is gone again.
Thanks. I suppose then I'm looking for good, and half and half of fast and cheap, or if not then simply good and cheap and I'll accept the lesser bandwidth. -- Jeff Wheeler Postmaster, Network Admin US Institute of Peace On Aug 4, 2004, at 5:42 PM, Robert Waldner wrote:
On Wed, 04 Aug 2004 17:25:43 EDT, Jeff Wheeler writes:
I'm getting somewhat frustrated with the instability and high latency of residential cable and DSL offerings, but I love the T1 or greater bandwidth they offer. I'd like reasonable bandwidth with low latency without spending hundreds of dollars per month!
RFC 1925, 7a.
cheers, &rw -- -- Dawn is nature's way of telling you to go to bed. -- -> And to just stay there until the evil yellow -- disk is gone again.
On Wed, Aug 04, 2004 at 11:06:31PM -0400, Jeff Wheeler wrote:
Thanks. I suppose then I'm looking for good, and half and half of fast and cheap, or if not then simply good and cheap and I'll accept the lesser bandwidth.
Unsure if you've used them, but I've been extremely pleased with Speakeasy and their DSL offerings. We used an SDSL line for a remote office and never had a problem with it. Currently have one of their OneLink (dry pair ADSL) lines up, and will probably have another installed soon. Short of that, being in Texas, I can't really help with any fixed wireless tips. Wes -- FreeBSD administrator, tmb.org Hosting wesmills@wyvern.org
Assuming your router supports it and assuming you are primarily browsing, not serving requests, you may want to try one of each. A low-end DSL and cable connection. The chances of both being flakey at the same moment are pretty low [in my experience] and your router should be able to detect fairly quickly if something is amiss. Then again, I have seen at least 50% of the instability-with-DSL complaints in the last 1 year be related to a bad OS on a router or just a bad router that flakes periodically. DJ Jeff Wheeler wrote:
Thanks. I suppose then I'm looking for good, and half and half of fast and cheap, or if not then simply good and cheap and I'll accept the lesser bandwidth.
-- Jeff Wheeler Postmaster, Network Admin US Institute of Peace
On Aug 4, 2004, at 5:42 PM, Robert Waldner wrote:
On Wed, 04 Aug 2004 17:25:43 EDT, Jeff Wheeler writes:
I'm getting somewhat frustrated with the instability and high latency of residential cable and DSL offerings, but I love the T1 or greater bandwidth they offer. I'd like reasonable bandwidth with low latency without spending hundreds of dollars per month!
RFC 1925, 7a.
cheers, &rw -- -- Dawn is nature's way of telling you to go to bed. -- -> And to just stay there until the evil yellow -- disk is gone again.
Jeff Wheeler wrote:
Anybody know a good source for near-T1 low-latency bandwidth at around $100/month? I'm in the northern VA area btw.
Hi Jeff. I don't know where you are in Northern VA, but, Skynet offers wireless access in eastern Loudoun County with coverage in Leesburg, Sterling and Ashburn. http://www.skynetaccess.com/wdsl.html Hope this helps Jeff
On Wed, 4 Aug 2004, Jeff Wheeler wrote:
Anybody know a good source for near-T1 low-latency bandwidth at around $100/month? I'm in the northern VA area btw.
How much is "low latency"? I have 6ms RTT over my 8M/800k ADSL, it's usually 6-8ms over an equivalent 2M g.shdsl line. -- Mikael Abrahamsson email: swmike@swm.pp.se
How much is "low latency"? I have 6ms RTT over my 8M/800k ADSL, it's usually 6-8ms over an equivalent 2M g.shdsl line.
interesting question. i have two adsl lines. pinging the first hop router verizon / lavanet (hawi to honolulu, 25 mins air time by plane) 64 bytes from 64.65.95.73: icmp_seq=0 ttl=64 time=20.637 ms 64 bytes from 64.65.95.73: icmp_seq=1 ttl=64 time=22.186 ms 64 bytes from 64.65.95.73: icmp_seq=2 ttl=64 time=21.965 ms 64 bytes from 64.65.95.73: icmp_seq=3 ttl=64 time=21.723 ms 64 bytes from 64.65.95.73: icmp_seq=4 ttl=64 time=21.538 ms qwest / iinet (30 miles from bainbridge to hellview wa us) 64 bytes from 209.20.186.1: icmp_seq=0 ttl=63 time=67.008 ms 64 bytes from 209.20.186.1: icmp_seq=1 ttl=63 time=67.700 ms 64 bytes from 209.20.186.1: icmp_seq=2 ttl=63 time=56.696 ms 64 bytes from 209.20.186.1: icmp_seq=3 ttl=63 time=60.249 ms i do not know why and can get no useful info on provisioning. i know iinet is redback. randy
On Wed, 4 Aug 2004, Randy Bush wrote:
How much is "low latency"? I have 6ms RTT over my 8M/800k ADSL, it's usually 6-8ms over an equivalent 2M g.shdsl line.
interesting question. i have two adsl lines. pinging the first hop router
Perhaps I should point out that in both my cases the IP router is in the CO and the ATM connection is only the actual physical DSL connection. -- Mikael Abrahamsson email: swmike@swm.pp.se
verizon / lavanet (hawi to honolulu, 25 mins air time by plane)
64 bytes from 64.65.95.73: icmp_seq=0 ttl=64 time=20.637 ms 64 bytes from 64.65.95.73: icmp_seq=1 ttl=64 time=22.186 ms 64 bytes from 64.65.95.73: icmp_seq=2 ttl=64 time=21.965 ms 64 bytes from 64.65.95.73: icmp_seq=3 ttl=64 time=21.723 ms 64 bytes from 64.65.95.73: icmp_seq=4 ttl=64 time=21.538 ms
qwest / iinet (30 miles from bainbridge to hellview wa us)
64 bytes from 209.20.186.1: icmp_seq=0 ttl=63 time=67.008 ms 64 bytes from 209.20.186.1: icmp_seq=1 ttl=63 time=67.700 ms 64 bytes from 209.20.186.1: icmp_seq=2 ttl=63 time=56.696 ms 64 bytes from 209.20.186.1: icmp_seq=3 ttl=63 time=60.249 ms
i do not know why and can get no useful info on provisioning. i know iinet is redback.
It's more than likely interleaving which is causing the latency, it's used in order to reduce line errors (and to increase reach) but a side effect is that it increases latency. The verizon connection is more than likely not using interleaving while the Qwest connection is. John -- John Lyons Phone: +353-1-660-9040 Network Engineer Fax: +353-1-660-3666 HEAnet Ltd. Email: john.lyons@heanet.ie
On Wed, 4 Aug 2004, Randy Bush wrote:
How much is "low latency"? I have 6ms RTT over my 8M/800k ADSL, it's usually 6-8ms over an equivalent 2M g.shdsl line.
interesting question. i have two adsl lines. pinging the first hop router
verizon / lavanet (hawi to honolulu, 25 mins air time by plane)
64 bytes from 64.65.95.73: icmp_seq=0 ttl=64 time=20.637 ms 64 bytes from 64.65.95.73: icmp_seq=1 ttl=64 time=22.186 ms 64 bytes from 64.65.95.73: icmp_seq=2 ttl=64 time=21.965 ms 64 bytes from 64.65.95.73: icmp_seq=3 ttl=64 time=21.723 ms 64 bytes from 64.65.95.73: icmp_seq=4 ttl=64 time=21.538 ms
qwest / iinet (30 miles from bainbridge to hellview wa us)
64 bytes from 209.20.186.1: icmp_seq=0 ttl=63 time=67.008 ms 64 bytes from 209.20.186.1: icmp_seq=1 ttl=63 time=67.700 ms 64 bytes from 209.20.186.1: icmp_seq=2 ttl=63 time=56.696 ms 64 bytes from 209.20.186.1: icmp_seq=3 ttl=63 time=60.249 ms
i do not know why and can get no useful info on provisioning. i know iinet is redback.
Looks like Qwest are using data interleaving on their connection, while Verizon aren't. It helps reduce dataloss at the expense of increased latency, by interleaving bits over time so that a short burst of signal destroying noise can only remove part of any given larger block. Data blocks reserve some space for error-correction data, which can salvage a partially damaged block. I hear a lot of ISPs in the states are turning on interleaving by default these days, while in the UK I've never actually encountered it. Some ADSL modems have an option to disable it also. Sam
On 06.08.2004 15:10 Sam Stickland wrote:
I hear a lot of ISPs in the states are turning on interleaving by default these days, while in the UK I've never actually encountered it. Some ADSL modems have an option to disable it also.
Here in Germany interleaving is default. You may order "FastPath" as additional "service" (~ 1.5$ extra). Mostly gamers want to have FastPath enabled to cut down RTT. Arnold
On Fri, 6 Aug 2004, Arnold Nipper wrote:
On 06.08.2004 15:10 Sam Stickland wrote:
I hear a lot of ISPs in the states are turning on interleaving by default these days, while in the UK I've never actually encountered it. Some ADSL modems have an option to disable it also. Here in Germany interleaving is default. You may order "FastPath" as additional "service" (~ 1.5$ extra). Mostly gamers want to have FastPath enabled to cut down RTT.
If you want low-latency you dont use ADSL. My SDSL connection: rtt min/avg/max/mdev = 2.454/2.544/6.587/0.187 ms -Dan
On Fri, 6 Aug 2004, Dan Hollis wrote:
If you want low-latency you dont use ADSL.
My SDSL connection:
rtt min/avg/max/mdev = 2.454/2.544/6.587/0.187 ms
I guess this is because it uses flame delay instead of ATM? If it wasn't for ADSL and g.SHDSL I guess nobody would still use ATM? Let's hope the VDSL guys sort out their range problems (5.5km) so we can all get on with our lives without ever using ATM again. -- Mikael Abrahamsson email: swmike@swm.pp.se
On 06.08.2004 20:51 Dan Hollis wrote:
If you want low-latency you dont use ADSL.
My SDSL connection:
rtt min/avg/max/mdev = 2.454/2.544/6.587/0.187 ms
At least here in Germany, SDSL is much more expensive than ADSL. Hence using FastPath may make sense ... Arnold btw: what does your rtt show? The *DSL path may me much shorter than from you to the next IP hop.
participants (11)
-
Arnold Nipper -
Dan Hollis -
Deepak Jain -
Jeff Cole -
Jeff Wheeler -
John Lyons -
Mikael Abrahamsson -
Randy Bush -
Robert Waldner -
Sam Stickland -
Wes Mills