Quote:
Originally Posted by argov
Requested Data Rate, I don't remember this number as high before the update but, as I said above, speed actually are slower in the past 2 weeks.
|
Well, as you said, it is the
Requested Data Rate and not actual throughput. I just took a look at my RDR while grabbing a 3MB file via PIE and I maxed out at ~614 kbps on my RDR. I am currently in the one of the "student computer areas" of my campus (UTSA) and my Rx Power is fairly sensitive on campus and jumps from -78 dbm up to -89 dbm in this area (and that is decent for being on campus). I have noticed a higher RDR in the past whenever I have been in an area with a stable signal and overall stronger reception (e.g. - my apartment).
From this and my previous experience, I have a few plausible conclusions.
1. The more stable a connection (not fluctuating as much) and better the reception, the higher the RDR. A good example of this would be with Wi-Fi. If you are fairly close to a 802.11G access point that you are using and have a 802.11G card in a laptop that you using, you may see that you are "connected at 54 Mbps". The further you go away and/or the more interference (and thus a less stable connection) there is, the slower your speed will be connected at (I forgot all of the fall back rates, but I think that is something around 54, 48, 36, 24, 18, 11, 5, 3, 2 and 1). Even though it may state that you are "connected at 54 Mbps", you can NEVER achieve that throughput in the real world due to overhead and general interference that causes dropped packets and other non-fun things. You may be able to transfer at max 20Mbps when "connected at 54 Mbps".
To sum it up: The "Requested Data Rate" is exactly that, the "Requested Data Rate" and signal strength and stability can make that RDR go slower than 2562.000 kbps to keep the connection from dropping.
2. Tons of users on the tower that you are currently using. Towers have only so much to share and are forced to allocate bandwidth as evenly as possible among all of the cell tower's users. Although on second thought, this may not be valid for the RDR value since the RDR value seems to be on the phone/client side of things.
3. A combination and 1 + 2.
And now to jump back onto Rev-A.
Quote:
Originally Posted by TC1
That's a very legitimate question. From the info I've gathered, EVDO Rev A support has nothing to do with Sprint or HTC.... it's Microsoft's fault. In other words, Sprint's infrastructure is capable of Rev A, HTC's hardware (the Titan) is capable, but WM6 does not support Rev A yet. That's why the rumors abound that Rev A will be ready around Q1 2008 because that is also the rumored time period that Microsoft themselves will release a service pack or new revision of WM6.
So as bad as Sprint is, this one might not be their fault. But everything else is, lol.
|
Any links to external articles or info about this? I would find it to be an interesting read. Hopefully Rev. A does come to fruition for the 6800. In the meanwhile, I'll be content with my 6700.
Eeek! Time to run off to my Accounting Lab!