The company responds to reports of lag in World of Warcraft's S
-
Posted by Clara Charlotte - Filed in Arts & Culture - 637 views
Blizzard Entertainment says it is "working very hard" to figure out what is causing the lag in the Sanctum of Domination raid in World of Warcraft. A "burst of lag" that occurred during phase one of the Sylvanas Windrunner encounter, in particular, has resulted in a large number of player complaints.
This is due to a "higher-than-usual" number of calculations being performed at the start of the fight in order to "facilitate the complex mechanics" of the three-phase encounter, according to a Blue post published on August 25 by Blizzard. The developers are looking into possible solutions, but they are taking care not to alter the design or mechanics of the boss in any way of farming wow tbc gold.
“While we believe we can make improvements over time, there will still be a few seconds of server lag on pull for the time being,” Blizzard stated.
After removing reports of lag during the encounter's initial burst, the developers are "diagnosing" reports of lag during "almost every" phase of the fight. They have not, however, been able to reproduce the lag in a testing environment.
According to Blizzard, “in addition to our own internal testing, when we utilized our performance analysis tools on actual live raids that reported experiencing lag, the server always appeared to be functioning smoothly.”
Eventually, the developers discovered that the Sylvanas fight was "very messaging-heavy" and that the mechanics involved necessitated the sending of "many frequent updates" to the player's game client, which was "very frustrating."
In combination with the "accumulated changes," an "unrelated change" in how the developers organize and distribute server processes across their server hardware caused their server processes to become more "concentrated."
The combination of these factors results in the lag, according to the developers.
During World of Warcraft's most recent weekly maintenance, the developers implemented several changes to how they "distribute" server processes, which should help to alleviate the source of the problem.