I never liked the terms "upload" and "download". I think "inload" and "outload" might be better, just because they don't carry implications of subordination or unequal required effort.
As it happens most of our home connections are asymmetrical: much higher coming in than going out.Om Malik reports how poorly his "high speed" connection works for backup over the Net: approximately 90Kbps on the outbound, even though the inbound is around 9Mbps — the claimed speed for Covad's ADSLs+ connection was "up to 15Mbps".
I'm not sure why his connection is so slow. Is all ADSL sucky as well as asymmetrical? I dunno. I've never had ADSL.
Up until '96 I had dial-up. Then from '96-97 I had Metricom's wireless Ricochet, which promised 33Kbps, but rarely reached that speed. Then, at my last house in the Bay Area, I got Covad/Concentric's IDSL, which (as I understood it) was IDSN tricked up to resemble DSL. There the deal was 110Kbps symmetrical, plus sixteen IP addresses. I ran servers out of the house on that speed.
One reason I was glad to move to Santa Barbara was much higher-speed Internet connectivity through the local cable provider, which was Cox. At first the measured speeds were as much as 7Mbps on the downstream and 1Mbps on the upstream. That was when Cox was using @Home's backhaul. Then they switched to their own and "improved" service by making it slower: 3Mbps down and 300Kbps up. More recently I've been getting their maximum, which is 5Mbps down and 1Mbps up. And it delivers as promised.
Here at my apartment near Boston, my Internet is provided by Verizon FiOS, which delivers 20Mb symmetrical service for $60-something per month. I test it often, and it's solid. I haven't set up an offsite backup system yet (not for whole drives anyway recommendations welcome), but I have no trouble uploading full-size photos by the bucketload, both to my own Flickr account (now approaching 28,000 shots) and Linux Journal's photo collection.
Still, it seems to me that the promise of "cloud" and "utility" computing remains conditional at best for those with connections as bad as Om's. Which is most of us, I presume.
I just got back from Freedom To Connect, where speeds are of the essence. A 65Mb fiber connection was shared there, and the connectivity in both directions was rock solid. This was almost a New Thing in my experience of conferences. The week before at SXSW, a much larger conference, the connectivity was also solid, though not quite as fast. That was the only conference I've ever attended at which the cell phone service (by AT&T at least) was hosed (by an abundance of iPhones), while the wi-fi was reliable. Usually it's the other way around.
Maverick: I feel the need...
Maverick, Goose: ...the need for speed!
I sense that the whole culture is starting to feel the same way.
Starting, that is. Most non-geeks still hardly care.
But the time is coming when we're all going to want the connectivity equivalent of hot and cold running water, of paved roads, of 100+ amp electric service.
Much of F2C was about what would be done with the $7.x billion devoted in the "stimulus" plan to "broadband" upgrades. Right now I worry that the whole thing causes a market distortion that might do more harm than good. Or, put more kindly, might do less good than the plan hopes for.
Still, I think that the demand for better service will grow. And the market, in whatever shape it takes (which right now appears to include many more "munis" -- municipalities), will respond with better speeds.
Because the need will be there.
Doc Searls is Senior Editor of Linux Journal
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- RSS Feeds
- Readers' Choice Awards
- Tech Tip: Really Simple HTTP Server with Python
3 hours 31 min ago
- Reply to comment | Linux Journal
4 hours 4 min ago
- All the articles you talked
6 hours 27 min ago
- All the articles you talked
6 hours 30 min ago
- All the articles you talked
6 hours 32 min ago
10 hours 56 min ago
- Keeping track of IP address
12 hours 47 min ago
- Roll your own dynamic dns
18 hours 1 min ago
- Please correct the URL for Salt Stack's web site
21 hours 12 min ago
- Android is Linux -- why no better inter-operation
23 hours 28 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?