Well, here is a few things most, if not all, of you guys wouldn't know about the lag in gunz.
ping is a good teller of lag but not in all cases. if you and someone have over 70 ping to eachother, obviously there is lag there. But, some of you have probably noticed that someone with 30 ping can feel like they have 130, and you need to lead them accordingly.
Well, im here to explain some of that and tell you what you can do to fix it.
Packet Queuing
packet queuing is when you have multiple computers in your household running off of 1 router.
when your computer cant handle all the information coming in at the same time, it makes the packets wait in a line. this causes you to have to wait longer for info. You cannot tell if someone has packet queuing going on, but ill give a link at the end of this post to find out if you have this going on at your home. packet queuing is caused by SLOW ROUTERS.
Network Congestion
network congestion is caused by the people in your neighborhood using the bandwidth alloted by the isp's node. This is similar to packet queuing but not just your household, its your whole block or more. This wil also make your packets wait in a line. think of it like your whole block connection to 1 big router. the link at the end will also detect this. you cannot fix this except by getting a new isp.
Tracerts
tracert stands for traceroute. A traceroute shows the time it takes from one place to another, kind of like ping, but it also displays the time between each "hop" in between.
here is an example, this is my traceroute to google.com
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\danny>tracert google.com
Tracing route to google.com [72.14.207.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 10 ms 6 ms xx.xxx.xxx.x
3 14 ms 11 ms 7 ms ge-1-44-ur01.mchenry.il.chicago.comcast.net [68.
85.208.169]
4 11 ms 13 ms 13 ms te-3-1-ur02.algonquin.il.chicago.comcast.net [68
.87.230.25]
5 15 ms 11 ms 16 ms te-8-4-ur01.algonquin.il.chicago.comcast.net [68
.87.231.233]
6 12 ms 11 ms 13 ms po-10-ar01.area4.il.chicago.comcast.net [68.87.2
29.110]
7 12 ms 15 ms 11 ms te-3-1-ar01.chartford.ct.hartford.comcast.net [6
8.86.90.58]
8 13 ms 12 ms 11 ms pos-0-3-0-0-cr01.chicago.il.ibone.comcast.net [6
8.86.90.57]
9 14 ms 14 ms 13 ms xe-9-0-0.edge1.Chicago2.Level3.net [4.71.248.33]
10 17 ms 18 ms 17 ms ae-31-51.ebr1.Chicago1.Level3.net [4.68.101.30]
11 42 ms 40 ms 50 ms ae-2.ebr2.NewYork1.Level3.net [4.69.132.66]
12 52 ms 53 ms 54 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.134.94]
13 42 ms 51 ms 40 ms ae-4-99.edge1.NewYork1.Level3.net [4.68.16.206]
14 44 ms 44 ms 44 ms GOOGLE-INC.edge1.NewYork1.Level3.net [4.71.172.8
6]
15 40 ms 41 ms 48 ms 216.239.43.146
16 48 ms 45 ms 46 ms 66.249.94.92
17 42 ms 39 ms 49 ms 66.249.94.50
18 43 ms 47 ms 40 ms eh-in-f99.google.com [72.14.207.99]
Trace complete.
This is VERY useful if your having packet loss or lagging really bad and want to find the reason why. here is how you can tell if your having issues in your household and u can fix them.
hop 1 <1 ms <1 ms <1 ms 192.168.0.1 this is to your router(if you have one) or to your modem if you dont have a router. this should always be <1 if its going to your router. if this is greater then 4 or 5, you might have faulty cables.
hop 2 10 ms 10 ms 6 ms xx.xxx.xxx.x if you have a router then this is to your modem, it should be pretty constant in ms, mine is a little off. if you see a huge jump, like
8ms 8ms 35ms then you have an issue, faulty cables and electromagnetic waves can cause this, move the modem away from anything running on electricty to fix it.
if you dont have a router then this hop goes to your blocks node, a real high lag time here can mean faulty cabling and youd need to call your isp to have them come replace them.
a traceroute is done by clicking start then run then typing cmd. when you get to the prompt type tracert google.com or someother address.
THE LINK!!!!!!!
this link here will tell you your upload and download speed.
after the test is done click on statistics and it will tell you if you are getting any packet queuing and also if your network is congested.
UC Santa CruZ NDT server
if any of you have questions just ask, ill be happy to help.
i hope some of you can fix some lag issues.
with no network congestion and no packet queuing i dont have to lead AT ALL on anyone under 70 ping, cool huh?
PEACE