HSDPA & Gaming

N

nictron

Senior Member
Joined
Mar 1, 2004
Messages
535
Hi All

I would like to know if 3G/HSDPA is any good for gaming?

Let’s say that you have the ideal situation, full signal and external antenna.

Would the latencies still be high or would it be acceptable?

I had ADSL in Potchefstroom and I have to move to Johannesburg and I have friends who have been waiting 3 Months for their ADSL.

And to be honest I just don’t want to wait that long, so if there is any other options for gaming I would appreciate your assistance.

Regards

Nictron

Just to add, I need steady latencies below 500, should not jump above 500ms to European and American servers.
 
Last edited by a moderator:
V

vodacom3g

Vodacom Representative
Joined
Jan 14, 2005
Messages
12,065
nictron said:
Just to add, I need steady latencies below 500, should not jump above 500ms to European and American servers.
Click to expand...

Under ideal conditions, to a local server, HSDPA will give around 100 - 120ms.

Real world, international speeds will be longer. I'm sure some of the gamers will have better information.
 
N

Nokkie

Executive Member
Joined
Dec 7, 2005
Messages
9,727
HSDPA is find for games like WOW, Command and Qonquer that tipes of rpg' but not so good for first person shooters
 
R

rabbiddog

Expert Member
Joined
Dec 29, 2004
Messages
1,219
www.gamespy.com

Pinging appscs.gamespy.com [216.35.19.179] with 32 bytes of data

Reply from 216.35.19.179: bytes=32 time=592ms TTL=237
Reply from 216.35.19.179: bytes=32 time=587ms TTL=236
Reply from 216.35.19.179: bytes=32 time=868ms TTL=237
Reply from 216.35.19.179: bytes=32 time=578ms TTL=236
Reply from 216.35.19.179: bytes=32 time=572ms TTL=236
Reply from 216.35.19.179: bytes=32 time=572ms TTL=237
Reply from 216.35.19.179: bytes=32 time=572ms TTL=236
Reply from 216.35.19.179: bytes=32 time=662ms TTL=237
Reply from 216.35.19.179: bytes=32 time=592ms TTL=237
Reply from 216.35.19.179: bytes=32 time=572ms TTL=236
Reply from 216.35.19.179: bytes=32 time=562ms TTL=237
Reply from 216.35.19.179: bytes=32 time=577ms TTL=236
Reply from 216.35.19.179: bytes=32 time=586ms TTL=236
Reply from 216.35.19.179: bytes=32 time=567ms TTL=237
Reply from 216.35.19.179: bytes=32 time=586ms TTL=236
Reply from 216.35.19.179: bytes=32 time=787ms TTL=237
Reply from 216.35.19.179: bytes=32 time=877ms TTL=237
Reply from 216.35.19.179: bytes=32 time=886ms TTL=236
Reply from 216.35.19.179: bytes=32 time=567ms TTL=237

Ping statistics for 216.35.19.179:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 562ms, Maximum = 886ms, Average = 640ms

Tracing route to appscs.gamespy.com [216.35.19.179]
over a maximum of 30 hops:

1 374 ms 436 ms 481 ms 10.113.238.162
2 338 ms 418 ms 551 ms 10.113.238.162
3 357 ms 581 ms 548 ms 196-207-44-149.gprs.vodacom.co.za [196.207.44.149]
4 360 ms 537 ms 499 ms 196-207-44-132.gprs.vodacom.co.za [196.207.44.132]
5 320 ms 404 ms 685 ms rrba-ip-esr-1-wan.telkom-ipnet.co.za [196.25.239.181]
6 648 ms 688 ms 711 ms ash-ip-dir-equinix-pos-6-1.telkom-ipnet.co.za [196.43.9.146]
7 819 ms 799 ms * pos2-0.cr02.ash01.pccwbtn.net [63.218.94.17]
8 689 ms 638 ms 651 ms cpr2-ge-5-0.virginiaequinix.savvis.net [208.173.50.201]
9 704 ms 709 ms 768 ms bcs1-so-3-1-0.Washington.savvis.net [208.173.10.202]
10 843 ms 1490 ms 921 ms dcr1-so-0-3-0.Chicago.savvis.net [204.70.192.26]
11 839 ms 880 ms 1029 ms dcr2-so-2-0-0.Denver.savvis.net [204.70.192.133]
12 1089 ms 968 ms 991 ms dcr1-so-2-0-0.SanFranciscosfo.savvis.net [204.70.192.114]
13 875 ms 879 ms 859 ms dcr1-as0-0.LosAngeles.savvis.net [204.70.192.117]
14 * 833 ms 869 ms dcr2-so-2-0-0.SanFranciscosfo.savvis.net [204.70.192.90]
15 1359 ms 889 ms 839 ms bhr1-pos-13-0.SantaClarasc4.savvis.net [208.172.147.106]
16 848 ms 1038 ms 1030 ms csr1.sc4.savvis.net [216.34.2.235]
17 1191 ms 958 ms 1119 ms 216.35.19.179

Trace complete.

www.westwood.com

Pinging napdhome.pogo.com [159.153.235.27] with 32 bytes of data:

Reply from 159.153.235.27: bytes=32 time=376ms TTL=113
Reply from 159.153.235.27: bytes=32 time=357ms TTL=113
Reply from 159.153.235.27: bytes=32 time=357ms TTL=113
Reply from 159.153.235.27: bytes=32 time=878ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=418ms TTL=113
Reply from 159.153.235.27: bytes=32 time=428ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113
Reply from 159.153.235.27: bytes=32 time=358ms TTL=113

Ping statistics for 159.153.235.27:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 357ms, Maximum = 878ms, Average = 386ms

Tracing route to napdhome.pogo.com [159.153.235.27]
over a maximum of 30 hops:

1 * 1841 ms 100 ms 10.113.238.162
2 98 ms 129 ms 89 ms 10.113.238.162
3 104 ms 119 ms 100 ms 196-207-44-149.gprs.vodacom.co.za [196.207.44.149]
4 104 ms 119 ms 100 ms 196-207-44-132.gprs.vodacom.co.za [196.207.44.132]
5 106 ms 120 ms 99 ms rrba-ip-esr-1-wan.telkom-ipnet.co.za [196.25.239.181]
6 337 ms 359 ms 359 ms ash-ip-dir-equinix-pos-6-1.telkom-ipnet.co.za [196.43.9.146]
7 394 ms 399 ms 379 ms pos2-0.cr02.ash01.pccwbtn.net [63.218.94.17]
8 427 ms 449 ms 379 ms Eth1-7.edge03.abn-iad.ea.com [206.223.115.55]
9 359 ms 379 ms 379 ms 159.153.224.222
10 395 ms 399 ms 449 ms fert05-eqx-iad.ea.com [159.153.224.134]
11 392 ms 389 ms 399 ms eaocore01-eqx-iad.ea.com [159.153.224.82]
12 405 ms 439 ms 400 ms www.ea.com [159.153.235.27]

Trace complete.
 
N

nictron

Senior Member
Joined
Mar 1, 2004
Messages
535
Thanx, those look interresting and might be playable. I am just worried about those jumps they can realy mess up a game.

And as i suspected the first jump to the tower is almost the biggest culprit. High in accordance to ADSL for instance.

Thanx again.
 
You must log in or register to reply here.
Top