Lag while raiding [Archive] - EQ2 Forum Archive @ EQ2Wire

Corellon

07-02-2009, 03:32 AM

To start this off, this is something I have been working on since TSO launch. Im not going to bother posting 3 posts worth of system info, as Im pretty positive its not my computer.Rough specs:CPU: Q6600GPU: BFG 9800GTXMem: 4 gigs ddr2OS: Windows 7As far as internet, I am getting approximately 1900 kbps down, 435 up. No packet loss now.With that out of the way, I am fine playing solo/group content. Whenever raiding however, around primetime in my area I sometimes suffer issues with seeming lag whenever mobs are pulled. I can run around, I get combat messages etc, but it gets increasingly delayed. For instance tonight, I said I was hitting my usual lag and it took near 3 minutes to even appear in groupchat. Other people see it even before I do on my own screen. This is obviously an issue on fights like Switchmaster that use raidwipe curses, etc.So with that said, this is what I have done myself to try and resolve it. I upgraded the PSU and mobo, increasing FSB, and making sure everything was getting enough power. My wife and I both play, she has the same exact thing happen to her so I didnt think it was specifically our PC hardware. Ive run tracerts and pings from my computer, from the router itself, and from the ISP service page. I also monitor connection statistics. I was getting a LITTLE bit of latency during peak times, around 150-200. Normally Im sitting at between 60-110. Everyonce in a while I would get a packet lost. Last week I was able to convince my cable provider to replace the line from my house to the pole. Restrung the whole thing, etc. I got a little bit of increase in bandwidth and the one or two packets lost went away. Again, reran tests etc, everything good. Fastforward to tonight, and the previously mentioned switchmaster fight. I immediately hit my lag, and end up having to pull the plug on my computer to avoid a raidwipe.With the consistantly intermittant (oxymoron, shush) difficulties Im having I am a liability to the raid. I have wiped us before to this, and if things continue will again. I have tried turning off my wifes computer, to no avail. Im not running torrent software. I have a linksys wrt54gl v1 running tomato 1.23 (Another attempt at fixing this). I have tried enabling ICMP, and disabling it. I had it portforwarding for a while, with no improvement.I have two final ideas about fixing this.1) Port Triggering. However I dont know how to configure this to work with the two pcs Im using to play.2) Im saturating my router. It reports 14.19 mb installed, and about 18% available. My thought is the router is running out of memory and cant keep up with the demand.I have read a bit about Nagles formula, not sure if thats a possibility, and have not enabled any QoS protocals- again a lack of knowledge how to set that up. Im considering purchasing a new router as the one I have was purchased around the release of the router, not sure if that would help. On average I have 4-5 devices connected to the router, 2 computers, my xbox, wii, iphone and printer- although most of those are turned off in the evening just in case.

Wullail

07-02-2009, 03:38 AM

<cite>Traakin@Antonia Bayle wrote:</cite><blockquote>1) Port Triggering. However I dont know how to configure this to work with the two pcs Im using to play.</blockquote>Port triggering for everquest 2 is the same as port forwarding except the port is opened when the game/PC sends data to that port , just set the triggering ports and the opened ports values to the same numbers in the start and finish boxes.Probibly a daft question but have you tried playing on one of the PCs only cutting out the router totally during a raid to see what happens?

Corellon

07-02-2009, 03:48 AM

Thats about the only thing I havent done, mostly because it occured to me tonight after I had left the raid. Hard to test with 23 other people waiting and a line of people wanting to join. Especially when it occurs intermittantly to begin with. Once its started though it doesnt get better. I have to leave, theres no sudden improvement.

Corellon

07-07-2009, 02:34 AM

<table style="border-collapse: collapse;" cellspacing="0" cellpadding="0" width="433" bordercolor="#111111"><tbody><tr><td width="433" height="25" align="center" bordercolor="#6666CC">So after causing issues for my raidforce again tonight I ran another traceroute, and got this. Opinions?traceroute to sdkeq2-04-01.everquest2.com (199.108.12.129), 30 hops max, 40 byte packets</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC"> 1 10.247.0.1 (10.247.0.1) 23.505 ms 23.943 ms 10.348 ms</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC"> 2 h17.23.198.12.cable.ptmg.cablerocket.net (12.198.23.17) 10.514 ms 34.467 ms 18.589 ms</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC"> 3 h1.23.198.12.cable.ptmg.cablerocket.net (12.198.23.1) 13.639 ms 11.977 ms 14.566 ms</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC"> 4 12.125.98.93 (12.125.98.93) 381.572 ms 416.315 ms 399.830 ms</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC"> 5 cr2.la2ca.ip.att.net (12.122.129.46) 385.281 ms 367.424 ms 333.160 ms</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC"> 6 cr2.sd2ca.ip.att.net (12.122.31.9) 340.182 ms 403.024 ms 371.063 ms</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC"> 7 gar3.sd2ca.ip.att.net (12.122.109.69) 436.809 ms 357.139 ms 472.012 ms</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC"> 8 mdf1-gsr12-2-pos-7-0.san2.attens.net (12.122.255.206) 387.579 ms 330.840 ms 324.350 ms</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC"> 9 mdf4-bi8k-2-eth-2-2.san2.attens.net (63.241.0.166) 318.439 ms 352.832 ms 326.007 ms</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC">10 vl20.sdkollsw-2.sonyonline.net (63.241.6.50) 345.435 ms 277.377 ms 299.769 ms</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC">11 sdkeq2-04-01.everquest2.com (199.108.12.129) 283.198 ms 290.357 ms 314.423 ms</td></tr><tr><td width="433" height="25" align="center" bordercolor="#6666CC">Trace complete</td></tr></tbody></table>

Corellon

07-07-2009, 02:47 AM

Ping statistics for 199.108.12.129: Packets: Sent = 200, Received = 200, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 183ms, Average = 69msAnd this was from about 5 minutes later. So I really have no clue now.

TSR-DanielH

07-07-2009, 05:00 PM

<cite>Wullail@Splitpaw wrote:</cite><blockquote>Probibly a daft question but have you tried playing on one of the PCs only cutting out the router totally during a raid to see what happens?</blockquote>If you haven't tried this yet then I would definitely suggest doing so at the next opportunity. If we can completely eliminate the router as a possible cause then that will help a lot when diagnosing the issue.

Corellon

07-19-2009, 02:02 PM

Well I changed providers.Ping statistics for 199.108.0.133: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 32ms, Maximum = 38ms, Average = 32msLets hope this bodes well.

TSR-DanielH

07-24-2009, 02:52 PM

<cite>Traakin@Antonia Bayle wrote:</cite><blockquote>Well I changed providers.Ping statistics for 199.108.0.133: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 32ms, Maximum = 38ms, Average = 32msLets hope this bodes well.</blockquote>Well, that definitely looks better than the last one you posted. Let us know how it turns out!