Results 1 to 7 of 7
- 03-13-2005, 11:51 PM #1Guest
What's to be expected from using EDGE? I did a test, ftp'ing a file
from a highly-accessible server, and got these speeds:
Signal strength 3 dots:
17.46 kB/s
17.49
15.26
Signal strength 4 dots: (moving 20 feet to another location)
22.03 kB/s
22.17
These are k-bytes/sec, and so with check-bits, etc, I'm used to
equating 10 bits with one byte. In other words, I've been getting
throughput (incoming), at 220 kpbs.
Is 220 kbps the best I ought to expect?
(This test was done in Portland, OR, where the app says "Roam / GPRS".)
› See More: Test: EDGE data speeds
- 03-14-2005, 04:32 AM #2efishtaGuest
Re: EDGE data speeds
<[email protected]> wrote in message
news:[email protected]...
> What's to be expected from using EDGE? I did a test, ftp'ing a file
> from a highly-accessible server, and got these speeds:
>
> Signal strength 3 dots:
> 17.46 kB/s
> 17.49
> 15.26
>
> Signal strength 4 dots: (moving 20 feet to another location)
> 22.03 kB/s
> 22.17
>
> These are k-bytes/sec, and so with check-bits, etc, I'm used to
> equating 10 bits with one byte. In other words, I've been getting
> throughput (incoming), at 220 kpbs.
Keep in mind that a byte = 8 bits, so if you want to do the math correctly,
it would be 22 KBps or 176 kbps.
>
> Is 220 kbps the best I ought to expect?
>
> (This test was done in Portland, OR, where the app says "Roam / GPRS".)
>
- 03-14-2005, 08:51 AM #3Tony ClarkGuest
Re: EDGE data speeds
"efishta" <[email protected]> wrote in message
news:[email protected]...
> <[email protected]> wrote in message
> news:[email protected]...
>> What's to be expected from using EDGE? I did a test, ftp'ing a file
>> from a highly-accessible server, and got these speeds:
>>
>> Signal strength 3 dots:
>> 17.46 kB/s
>> 17.49
>> 15.26
>>
>> Signal strength 4 dots: (moving 20 feet to another location)
>> 22.03 kB/s
>> 22.17
>>
>> These are k-bytes/sec, and so with check-bits, etc, I'm used to
>> equating 10 bits with one byte. In other words, I've been getting
>> throughput (incoming), at 220 kpbs.
>
> Keep in mind that a byte = 8 bits, so if you want to do the math
> correctly, it would be 22 KBps or 176 kbps.
>
SNIP
Yes but usually you have to include start and stop bits hence the reason
people use 10 as the multiplying factor.
TC
- 03-15-2005, 08:45 AM #4Bob L.Guest
Re: EDGE data speeds
Hi:
If you want to get specific you also need to remove the protocol items to
calculate a true data throughput. 10 bits is close enough.
Bob
"efishta" <[email protected]> wrote in message
news:[email protected]...
> <[email protected]> wrote in message
> news:[email protected]...
> > What's to be expected from using EDGE? I did a test, ftp'ing a file
> > from a highly-accessible server, and got these speeds:
> >
> > Signal strength 3 dots:
> > 17.46 kB/s
> > 17.49
> > 15.26
> >
> > Signal strength 4 dots: (moving 20 feet to another location)
> > 22.03 kB/s
> > 22.17
> >
> > These are k-bytes/sec, and so with check-bits, etc, I'm used to
> > equating 10 bits with one byte. In other words, I've been getting
> > throughput (incoming), at 220 kpbs.
>
> Keep in mind that a byte = 8 bits, so if you want to do the math
correctly,
> it would be 22 KBps or 176 kbps.
>
> >
> > Is 220 kbps the best I ought to expect?
> >
> > (This test was done in Portland, OR, where the app says "Roam /
GPRS".)
> >
>
>
--
I am using the free version of SPAMfighter for private users.
It has removed 1062 spam emails to date.
Paying users do not have this message in their emails.
Try www.SPAMfighter.com for free now!
- 03-23-2005, 11:20 AM #5John NavasGuest
Re: Test: EDGE data speeds
[POSTED TO alt.cellular.cingular - REPLY ON USENET PLEASE]
In <[email protected]> on 13 Mar 2005
21:51:11 -0800, "[email protected]" <[email protected]> wrote:
>What's to be expected from using EDGE? I did a test, ftp'ing a file
>from a highly-accessible server, and got these speeds:
>
>Signal strength 3 dots:
>17.46 kB/s
>17.49
>15.26
>
>Signal strength 4 dots: (moving 20 feet to another location)
>22.03 kB/s
>22.17
Those are good EDGE speeds.
>These are k-bytes/sec, and so with check-bits, etc, I'm used to
>equating 10 bits with one byte. In other words, I've been getting
>throughput (incoming), at 220 kpbs.
No, just 8-bit bytes ( this isn't async serial , so you're topping out at
about 180 Kbps.
>Is 220 kbps the best I ought to expect?
180 Kbps is the best you ought to expect.
Use Google Groups to find my prior posts with detailed performance data on
EDGE connections.
--
Best regards, HELP FOR CINGULAR GSM & SONY ERICSSON PHONES:
John Navas <http://navasgrp.home.att.net/#Cingular>
- 03-23-2005, 11:21 AM #6John NavasGuest
Re: EDGE data speeds
[POSTED TO alt.cellular.cingular - REPLY ON USENET PLEASE]
In <[email protected]> on Mon, 14 Mar 2005
14:51:10 GMT, "Tony Clark" <[email protected]> wrote:
>
>"efishta" <[email protected]> wrote in message
>news:[email protected]...
>> <[email protected]> wrote in message
>> news:[email protected]...
>>> What's to be expected from using EDGE? I did a test, ftp'ing a file
>>> from a highly-accessible server, and got these speeds:
>>>
>>> Signal strength 3 dots:
>>> 17.46 kB/s
>>> 17.49
>>> 15.26
>>>
>>> Signal strength 4 dots: (moving 20 feet to another location)
>>> 22.03 kB/s
>>> 22.17
>>>
>>> These are k-bytes/sec, and so with check-bits, etc, I'm used to
>>> equating 10 bits with one byte. In other words, I've been getting
>>> throughput (incoming), at 220 kpbs.
>>
>> Keep in mind that a byte = 8 bits, so if you want to do the math
>> correctly, it would be 22 KBps or 176 kbps.
>>
>SNIP
>
>Yes but usually you have to include start and stop bits hence the reason
>people use 10 as the multiplying factor.
There are no start and stop bits -- it's a synchronous stream, not start-stop
async.
--
Best regards, HELP FOR CINGULAR GSM & SONY ERICSSON PHONES:
John Navas <http://navasgrp.home.att.net/#Cingular>
- 03-23-2005, 11:22 AM #7John NavasGuest
Re: EDGE data speeds
[POSTED TO alt.cellular.cingular - REPLY ON USENET PLEASE]
In <[email protected]> on Tue, 15 Mar 2005 14:45:28
GMT, "Bob L." <[email protected]> wrote:
>If you want to get specific you also need to remove the protocol items to
>calculate a true data throughput. 10 bits is close enough.
It's actually only about 8 bits -- protocol overhead is quite low.
>"efishta" <[email protected]> wrote in message
>news:[email protected]...
>> <[email protected]> wrote in message
>> news:[email protected]...
>> > What's to be expected from using EDGE? I did a test, ftp'ing a file
>> > from a highly-accessible server, and got these speeds:
>> >
>> > Signal strength 3 dots:
>> > 17.46 kB/s
>> > 17.49
>> > 15.26
>> >
>> > Signal strength 4 dots: (moving 20 feet to another location)
>> > 22.03 kB/s
>> > 22.17
>> >
>> > These are k-bytes/sec, and so with check-bits, etc, I'm used to
>> > equating 10 bits with one byte. In other words, I've been getting
>> > throughput (incoming), at 220 kpbs.
>>
>> Keep in mind that a byte = 8 bits, so if you want to do the math
>correctly,
>> it would be 22 KBps or 176 kbps.
>>
>> >
>> > Is 220 kbps the best I ought to expect?
>> >
>> > (This test was done in Portland, OR, where the app says "Roam /
>GPRS".)
>> >
>>
>>
--
Best regards, HELP FOR CINGULAR GSM & SONY ERICSSON PHONES:
John Navas <http://navasgrp.home.att.net/#Cingular>
Similar Threads
- alt.cellular.verizon
- alt.cellular.nextel
- alt.cellular.nokia
- alt.cellular.cingular
- alt.cellular.sprintpcs
Vente de voitures
in Chit Chat