.
I reposted this because it goes along with what GarryL and I believe others said on return communication to the client from the servers. Hopefully if there are new eyes on the situation they will take our points into consideration if they haven't. We don't know one way or the other, so I have to go with they haven't.
"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."
"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."
1/27/12:
.
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.
.
.