You should think about using the test server to gather statistics. % dropped packets %corrupt %duplicates ...average link speed. server tick rate high, low, and median. Maybe using wireshark or something.
Then maybe investigate bandwidth limiters to test in house. this is a great OOB tool I have been using although I do not know its price tag. I imagine chunky. <a href="http://maxwell.iwl.com/" target="_blank">http://maxwell.iwl.com/</a>
But there are Linux tools that perform the same functions. <a href="http://stackoverflow.com/questions/130354/how-do-i-simulate-a-low-bandwidth-high-latency-environment" target="_blank">http://stackoverflow.com/questions/130354/...ncy-environment</a>
You could then switch back and forth ....
+ Repro and fix using in house tools. + Test in real world.
If you start with the statistic gathering you should be able to see progress besides what your gut tells you in gameplay. good luck and go team venture
I can provide a VM in Centro datacenter on the outskirts of London, with console access and good (gaming) uplinks (see: killercreation.co.uk).
VM so spec is up to you and has console/KVM access.
Pings performed at midnight GMT+0 from UK ADSL lines. Traceroutes include 1-2 extra hops than a standard consumer line since I route everything through a /29. Traceroutes first 1-2 hops obscured for privacy reasons.
<b>Ping and traceroute from an ADSL1 (8mb/512kb) residential connection is (AAIsp [www.aaisp.net.uk] on BT 20CN)</b>
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->Pinging 217.146.88.252 with 32 bytes of data: Reply from 217.146.88.252: bytes=32 time=18ms TTL=58 Reply from 217.146.88.252: bytes=32 time=18ms TTL=58 Reply from 217.146.88.252: bytes=32 time=17ms TTL=58 Reply from 217.146.88.252: bytes=32 time=18ms TTL=58
Ping statistics for 217.146.88.252: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 18ms, Average = 17ms<!--c2--></div><!--ec2-->
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->Tracing route to 217.146.88.252 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms unknown [192.168.1.1] 2 1 ms <1 ms <1 ms **.**.187.81.in-addr.arpa [81.187.**.**] 3 13 ms 13 ms 12 ms b.gormless.thn.aaisp.net.uk [90.155.53.12] 4 14 ms 13 ms 17 ms a.armless.thn.aaisp.net.uk [90.155.53.6] 5 13 ms 13 ms 12 ms linx.killercreation.co.uk [195.66.225.123] 6 17 ms 16 ms 16 ms 217.146.94.6 [217.146.94.6] 7 18 ms 18 ms 17 ms 217.146.88.252
Trace complete.<!--c2--></div><!--ec2-->
<b>Ping and traceroute from an ADSL2 (16mb/1mb) residential connection is (Nildram, now Opal [www.nildram.co.uk] on BT LLU)</b>
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->PING 217.146.88.252 (217.146.88.252) 56(84) bytes of data. 64 bytes from 217.146.88.252: icmp_seq=0 ttl=56 time=23.5 ms 64 bytes from 217.146.88.252: icmp_seq=1 ttl=56 time=21.6 ms 64 bytes from 217.146.88.252: icmp_seq=2 ttl=56 time=22.1 ms 64 bytes from 217.146.88.252: icmp_seq=3 ttl=56 time=22.8 ms
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->traceroute to 217.146.88.252 (217.146.88.252), 30 hops max, 38 byte packets 1 84.12.***.** (84.12.***.**) 1.013 ms 0.894 ms 0.725 ms 2 * * * 3 10.72.4.66 (10.72.4.66) 16.408 ms 16.729 ms 15.972 ms 4 10.72.4.188 (10.72.4.188) 16.491 ms 17.244 ms 16.700 ms 5 xe-9-3-0.bragg002.loh.as13285.net (80.40.155.23) 16.705 ms 17.259 ms 74.665 ms 6 xe-7-3-0.scr001.loh.as13285.net (80.40.155.66) 17.429 ms 17.982 ms 18.468 ms 7 host-78-144-0-190.as13285.net (78.144.0.190) 17.471 ms 17.540 ms 17.477 ms 8 linx.killercreation.co.uk (195.66.225.123) 18.719 ms 18.068 ms 17.960 ms 9 217.146.94.6 (217.146.94.6) 22.427 ms 21.667 ms 21.720 ms 10 217.146.88.252 (217.146.88.252) 22.470 ms 22.039 ms 22.723 ms<!--c2--></div><!--ec2-->
<b>Ping and traceroute from 2xbonded ADSL1 (8mb/512kb) business connections is (Rural Communications [www.rcscumbria.co.uk] on BT 20CN)</b>
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->PING 217.146.88.252 (217.146.88.252) 56(84) bytes of data. 64 bytes from 217.146.88.252: icmp_seq=0 ttl=56 time=17.2 ms 64 bytes from 217.146.88.252: icmp_seq=1 ttl=56 time=17.9 ms 64 bytes from 217.146.88.252: icmp_seq=2 ttl=56 time=17.0 ms 64 bytes from 217.146.88.252: icmp_seq=3 ttl=56 time=17.1 ms
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1--> 1 192.168.1.251 (192.168.1.251) 0.301 ms 0.177 ms 0.197 ms 2 93.190.***.*** (93.190.***.***) 0.953 ms 0.587 ms 0.521 ms 3 93.190.118.1 (93.190.118.1) 13.492 ms 11.938 ms 11.348 ms 4 93.190.116.1 (93.190.116.1) 11.713 ms 12.043 ms 11.562 ms 5 vl210.mpd01.lon01.atlas.cogentco.com (149.6.2.97) 15.548 ms 12.304 ms 11.524 ms 6 te3-1.mpd02.lon01.atlas.cogentco.com (130.117.2.26) 12.151 ms te2-1.3493.mpd02.lon01.atlas.cogentco.com (130.117.2.18) 12.778 ms 12.353 ms 7 tiscali.lon01.atlas.cogentco.com (130.117.15.50) 17.772 ms 20.489 ms 18.206 ms 8 xe-10-2-0.lon10.ip4.tinet.net (89.149.185.169) 17.872 ms xe-0-3-0.lon10.ip4.tinet.net (89.149.185.226) 18.143 ms xe-10-2-0.lon10.ip4.tinet.net (89.149.185.169) 17.981 ms 9 tinet.killercreation.co.uk (77.67.65.34) 11.971 ms 12.756 ms 12.988 ms 10 217.146.94.6 (217.146.94.6) 17.056 ms 16.342 ms 15.775 ms 11 217.146.88.252 (217.146.88.252) 16.738 ms 16.832 ms 16.208 ms<!--c2--></div><!--ec2-->
<!--quoteo(post=1834874:date=Feb 25 2011, 12:39 PM:name=endar)--><div class='quotetop'>QUOTE (endar @ Feb 25 2011, 12:39 PM) <a href="index.php?act=findpost&pid=1834874"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->Do you have a problem with Australia?<!--QuoteEnd--></div><!--QuoteEEnd-->
Haha Endar your server seems so beefy it might not fit their 'real world' test requirement!
endarJoin Date: 2010-07-27Member: 73256Members, Squad Five Blue
I do have other machines which can match specs, but only if they are interested in Australia. After all I wouldn't want to take my server offline since this would not be a public server (right?).
Comments
% dropped packets %corrupt %duplicates ...average link speed. server tick rate high, low, and median.
Maybe using wireshark or something.
Then maybe investigate bandwidth limiters to test in house.
this is a great OOB tool I have been using although I do not know its price tag. I imagine chunky.
<a href="http://maxwell.iwl.com/" target="_blank">http://maxwell.iwl.com/</a>
But there are Linux tools that perform the same functions.
<a href="http://stackoverflow.com/questions/130354/how-do-i-simulate-a-low-bandwidth-high-latency-environment" target="_blank">http://stackoverflow.com/questions/130354/...ncy-environment</a>
You could then switch back and forth ....
+ Repro and fix using in house tools.
+ Test in real world.
If you start with the statistic gathering you should be able to see progress besides what your gut tells you in gameplay.
good luck
and
go team venture
VM so spec is up to you and has console/KVM access.
Pings performed at midnight GMT+0 from UK ADSL lines.
Traceroutes include 1-2 extra hops than a standard consumer line since I route everything through a /29.
Traceroutes first 1-2 hops obscured for privacy reasons.
<b>Ping and traceroute from an ADSL1 (8mb/512kb) residential connection is (AAIsp [www.aaisp.net.uk] on BT 20CN)</b>
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->Pinging 217.146.88.252 with 32 bytes of data:
Reply from 217.146.88.252: bytes=32 time=18ms TTL=58
Reply from 217.146.88.252: bytes=32 time=18ms TTL=58
Reply from 217.146.88.252: bytes=32 time=17ms TTL=58
Reply from 217.146.88.252: bytes=32 time=18ms TTL=58
Ping statistics for 217.146.88.252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 18ms, Average = 17ms<!--c2--></div><!--ec2-->
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->Tracing route to 217.146.88.252 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms unknown [192.168.1.1]
2 1 ms <1 ms <1 ms **.**.187.81.in-addr.arpa [81.187.**.**]
3 13 ms 13 ms 12 ms b.gormless.thn.aaisp.net.uk [90.155.53.12]
4 14 ms 13 ms 17 ms a.armless.thn.aaisp.net.uk [90.155.53.6]
5 13 ms 13 ms 12 ms linx.killercreation.co.uk [195.66.225.123]
6 17 ms 16 ms 16 ms 217.146.94.6 [217.146.94.6]
7 18 ms 18 ms 17 ms 217.146.88.252
Trace complete.<!--c2--></div><!--ec2-->
<b>Ping and traceroute from an ADSL2 (16mb/1mb) residential connection is (Nildram, now Opal [www.nildram.co.uk] on BT LLU)</b>
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->PING 217.146.88.252 (217.146.88.252) 56(84) bytes of data.
64 bytes from 217.146.88.252: icmp_seq=0 ttl=56 time=23.5 ms
64 bytes from 217.146.88.252: icmp_seq=1 ttl=56 time=21.6 ms
64 bytes from 217.146.88.252: icmp_seq=2 ttl=56 time=22.1 ms
64 bytes from 217.146.88.252: icmp_seq=3 ttl=56 time=22.8 ms
--- 217.146.88.252 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 21.681/22.548/23.529/0.709 ms, pipe 2<!--c2--></div><!--ec2-->
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->traceroute to 217.146.88.252 (217.146.88.252), 30 hops max, 38 byte packets
1 84.12.***.** (84.12.***.**) 1.013 ms 0.894 ms 0.725 ms
2 * * *
3 10.72.4.66 (10.72.4.66) 16.408 ms 16.729 ms 15.972 ms
4 10.72.4.188 (10.72.4.188) 16.491 ms 17.244 ms 16.700 ms
5 xe-9-3-0.bragg002.loh.as13285.net (80.40.155.23) 16.705 ms 17.259 ms 74.665 ms
6 xe-7-3-0.scr001.loh.as13285.net (80.40.155.66) 17.429 ms 17.982 ms 18.468 ms
7 host-78-144-0-190.as13285.net (78.144.0.190) 17.471 ms 17.540 ms 17.477 ms
8 linx.killercreation.co.uk (195.66.225.123) 18.719 ms 18.068 ms 17.960 ms
9 217.146.94.6 (217.146.94.6) 22.427 ms 21.667 ms 21.720 ms
10 217.146.88.252 (217.146.88.252) 22.470 ms 22.039 ms 22.723 ms<!--c2--></div><!--ec2-->
<b>Ping and traceroute from 2xbonded ADSL1 (8mb/512kb) business connections is (Rural Communications [www.rcscumbria.co.uk] on BT 20CN)</b>
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->PING 217.146.88.252 (217.146.88.252) 56(84) bytes of data.
64 bytes from 217.146.88.252: icmp_seq=0 ttl=56 time=17.2 ms
64 bytes from 217.146.88.252: icmp_seq=1 ttl=56 time=17.9 ms
64 bytes from 217.146.88.252: icmp_seq=2 ttl=56 time=17.0 ms
64 bytes from 217.146.88.252: icmp_seq=3 ttl=56 time=17.1 ms
--- 217.146.88.252 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 17.063/17.355/17.902/0.362 ms, pipe 2<!--c2--></div><!--ec2-->
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1--> 1 192.168.1.251 (192.168.1.251) 0.301 ms 0.177 ms 0.197 ms
2 93.190.***.*** (93.190.***.***) 0.953 ms 0.587 ms 0.521 ms
3 93.190.118.1 (93.190.118.1) 13.492 ms 11.938 ms 11.348 ms
4 93.190.116.1 (93.190.116.1) 11.713 ms 12.043 ms 11.562 ms
5 vl210.mpd01.lon01.atlas.cogentco.com (149.6.2.97) 15.548 ms 12.304 ms 11.524 ms
6 te3-1.mpd02.lon01.atlas.cogentco.com (130.117.2.26) 12.151 ms te2-1.3493.mpd02.lon01.atlas.cogentco.com (130.117.2.18) 12.778 ms 12.353 ms
7 tiscali.lon01.atlas.cogentco.com (130.117.15.50) 17.772 ms 20.489 ms 18.206 ms
8 xe-10-2-0.lon10.ip4.tinet.net (89.149.185.169) 17.872 ms xe-0-3-0.lon10.ip4.tinet.net (89.149.185.226) 18.143 ms xe-10-2-0.lon10.ip4.tinet.net (89.149.185.169) 17.981 ms
9 tinet.killercreation.co.uk (77.67.65.34) 11.971 ms 12.756 ms 12.988 ms
10 217.146.94.6 (217.146.94.6) 17.056 ms 16.342 ms 15.775 ms
11 217.146.88.252 (217.146.88.252) 16.738 ms 16.832 ms 16.208 ms<!--c2--></div><!--ec2-->
Thanks to all who has been in touch, May still get back to you at some stage.
Haha Endar your server seems so beefy it might not fit their 'real world' test requirement!