Test: EDGE data speeds

Toggle sidebar Toggle sidebar
G

Guest

Guest
Archived from groups: alt.cellular.cingular (More info?)

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".)
 
G

Guest

Guest
Archived from groups: alt.cellular.cingular (More info?)

<robb@acm.org> wrote in message
news:1110779471.204755.268380@l41g2000cwc.googlegroups.com...
> 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".)
>
 
G

Guest

Guest
Archived from groups: alt.cellular.cingular (More info?)

"efishta" <sorrydude@sorrydude.com> wrote in message
news:42356691$0$15414$9a6e19ea@unlimited.newshosting.com...
> <robb@acm.org> wrote in message
> news:1110779471.204755.268380@l41g2000cwc.googlegroups.com...
>> 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
 
G

Guest

Guest
Archived from groups: alt.cellular.cingular (More info?)

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" <sorrydude@sorrydude.com> wrote in message
news:42356691$0$15414$9a6e19ea@unlimited.newshosting.com...
> <robb@acm.org> wrote in message
> news:1110779471.204755.268380@l41g2000cwc.googlegroups.com...
> > 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!
 
G

Guest

Guest
Archived from groups: alt.cellular.cingular (More info?)

[POSTED TO alt.cellular.cingular - REPLY ON USENET PLEASE]

In <1110779471.204755.268380@l41g2000cwc.googlegroups.com> on 13 Mar 2005
21:51:11 -0800, "robb@acm.org" <robb@acm.org> 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>
 
G

Guest

Guest
Archived from groups: alt.cellular.cingular (More info?)

[POSTED TO alt.cellular.cingular - REPLY ON USENET PLEASE]

In <yxhZd.8670$oO4.6526@newsread3.news.pas.earthlink.net> on Mon, 14 Mar 2005
14:51:10 GMT, "Tony Clark" <curiousgeorge1964@hotmail.com> wrote:

>
>"efishta" <sorrydude@sorrydude.com> wrote in message
>news:42356691$0$15414$9a6e19ea@unlimited.newshosting.com...
>> <robb@acm.org> wrote in message
>> news:1110779471.204755.268380@l41g2000cwc.googlegroups.com...
>>> 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>
 
G

Guest

Guest
Archived from groups: alt.cellular.cingular (More info?)

[POSTED TO alt.cellular.cingular - REPLY ON USENET PLEASE]

In <cyCZd.138070$nC5.57929@twister.nyroc.rr.com> on Tue, 15 Mar 2005 14:45:28
GMT, "Bob L." <bob_lally@prophezine.com> 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" <sorrydude@sorrydude.com> wrote in message
>news:42356691$0$15414$9a6e19ea@unlimited.newshosting.com...
>> <robb@acm.org> wrote in message
>> news:1110779471.204755.268380@l41g2000cwc.googlegroups.com...
>> > 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>
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom