Quoted from "donmuerte;506736"
- do you use a router? Yes
- does it use NAT? Yes
- do you have software or hardware firewalls? Other than windows firewall, no
- anti-virus enabled/disabled? None
- what server are you on? (I wonder if this is specific to a few specific servers after the merge) Govinda
- DSL or cable and what is your bandwidth? Verizon Fios, 20 Mb down / 5 Mb Up
Quoted from "ipeacefrog;506745"
.
Very doubtfull it's user end.
Started with the move to the new data center. It's so widespread and all the ping times and tracerts posted from all over the country have looked just fine.
Quoted from "ipeacefrog;505706"
.
Based on the detailed info posted by myself as well as others, there should be a giant red arrow pointing in the general direction of the issue.
Example:
1) In Seige while I am Herald and having several min lag.
2) I click Fearless. Nothing happens on my screen.
3) Several in the guild get fearless instantly. Though still no cast on my end.
4) Several minutes later it finally casts on my screen. I along with others get fearless.
The same thing happens with killing ballons. I attack one. Nothing happens on my screen. Another person sees me kill it instantly on their screen. Minutes later the action happens on my screen.
I cast heals on the gate. Some see gate healing, some do not. Nothing happens on my screen till minutes later.
This type of action matches the examples we have been laying out here.
Clearly the client is immediately sending the action to the server, the server is immediately receiving it and passing it back to all involved clients. Some clients are receiving it right away, others much later.
Also, some log out get back in and the lag goes away or gets better. Others log out and back in and things get worse. This all assumes they actually get back in.
Some Seiges my lag builds but stays minnimal, other Seiges it builds and gets horrible. It's the same with everyone else in the guild. Every Seige part of the guild has bad lag, part has minnimal to moderate lag. It's different fro each person every night.
Looks to me like characters are being assigned to a given segment when they enter Seige and one of the segments is having issues keeping up.
So it appears to be a synchronization issue of some sort. Or an issue with some segment of server software/hardware getting backed up and slowly overloaded. Seems likely to be one of the segments handling the servers communication back to the client.
Since this started with the data center move, in the new center are you running on virtual servers or physical servers? What is different on the configuration between the old center and the new center? Questions you have likely asked, though an outsiders thoughts and questions can spark new thoughts and ideas.
One would think log files would also help sort this out, but what do I know I just own and operate an IT business.
We obviously enjoy Seige and would like it fixed. So we are making efforts to be patient and provide usefull info.
.
Quoted from "ipeacefrog;506918"
."Looks to me like characters are being assigned to a given segment when they enter Seige and one of the segments is having issues keeping up.
So it appears to be a synchronization issue of some sort. Or an issue with some segment of server software/hardware getting backed up and slowly overloaded. Seems likely to be one of the segments handling the servers communication back to the client."
Quoted from "donmuerte;506924"
So, I wonder if logging in a few minutes late would resolve things somehow. That reminds me, though, that a few of our members have been 30 minutes or so late to "enter battle" and they've reported not being able to get in at all.