Lakers,
re: "throughput" again
<< The speed issue is really a very fuzzy concept overall. >>
In mobile wireless telephony (mobile or portable) it certainly is.
It is considerably less fuzzy with fixed wired connections. In fact it is very consistent.
I know rather precisely what to expect from a wired modem connection in my home through my long standing exceptional local ISP. I know what my ADSL modem and V.90 modems will deliver in my home or office (which is attached to my home) over Verizon copper. and until I recently installed XP (the version of the Lucent monitoring tool I use doesn't yet support XP) I knew precisely what connection rate and throughput I was achieving in a given session from a particular web site.
If my connection rate and or throughput drop the Verizon techs get a call, look at my logs, and they splice or swap a cable because the darned squirrels chewed the fabric and its humid and the copper is singing. Alternatively I upload logs to my ISP, and they diagnose, although in the last 4 years the problem has never been on their end (except for feeds to them) but they have been helpful in helping diagnose a line problem.
That will not necessarily be the case in the early going with 1xRTT and I will use 1xRTT (assuming security and authentication pass muster for my Domino based corporate intranet) in a mobile or portable environment, but I suspect it will be some time before I eliminate ADSL with dial backup for fixed home or office although I'll certainly evaluate it.
<< There are two parts of the same thing, network throughput and the speed that a user gets. >>
All I'm interested in as a user is the speed I get, and the consistency of that speed.
<< The biggest challenge with networks is how to optimize the scheduler for all the users. Just like running a horse racing, you need a good horse and a good jockey combo to win. >>
With a wired connection, 1.2 miles from the Verizon switch, an exceptional ISP - matched modems and a modem to user ratio of better than 8:1 and great high speed feeds (actually 2 exceptional ISP's counting the company provided secured AT&T Worldnet connections I use on the road), well tuned modems, and great inside wiring. I have great horses, great jockeys and exceptional QoS.
Hopefully Verizon Wireless is a good horse and has a good jockey on the wireless data side.
Sprint PCS simply does not have adequate coverage where I travel to consider them for my primary wireless need - voice. My corporation has determined the same thing so we use AWS and Verizon corporately (with VoiceStream for overseas travel).
Sprint PCS doesn't even have adequate coverage where I reside and I am 1.4 miles from the major east coast north-south interstate that essentially stretches from Maine to Florida.
A Sprint PCS user can get a "fair" connection if he walks outside my office, sits on the front steps, and fiddles with the orientation of the handset. As the PCS website says:
The location you selected is only partially covered by the Sprint PCS Network. You may be unable to use your Sprint PCS Phone, or certain features may be unavailable in this area.
<< the average TP of a sector is about anywhere between 100kbps to 250kbps depending on number of users, distribution of the users, radio environment, applications and scheduling policy. >>
100 to 250 kbps average TP for the sector with Release 0?
<< depending on number of users >>
That’s just what I need - trying to surf at 9:15 in the evening with my wife and all my neighbors and all the students in the sorority and fraternity houses in my sector all talking on their free Verizon minutes.
As I say ... I suspect I'll be on copper for some time, and I really don't know what to expect from 1xRTT in the early going. I'm sure it will be much better than IS-95A for portability (phone as modem). I sure hope so. Right now that's "only in a pinch".
- Eric - |
