Blue Tracker
World of Warcraft Blue Posts
Diablo II: Resurrected Blue Posts
Diablo III Blue Posts
Hearthstone Blue Posts
Overwatch Blue Posts
Heroes of the Storm Blue Posts
Diablo IV Blue Posts
BlizzCon Blue Posts
Warcraft Rumble Blue Posts

19/02 Instance Performance Balancing

Forum Avatar
Wryxian
#0 - Feb. 19, 2009, 9:46 a.m.
Blizzard Post
To ensure stable and positive performance in raid and dungeon instances, an instance performance balancing feature was implemented which limits the total number of instances that can be created on a realm. Prior to this change, we were seeing serious issues in instances which greatly degraded instance performance, and in some cases, caused them to crash entirely.

This update instituted a load check that limited opening of additional instances. This will result in throttling of some instance creation where users receive the following message: "Additional instances could not be launched. Please, try again later." Ultimately, we felt that some wait time for players attempting to create a new instance was better than causing bad performance for all players in instances.

We are continually monitoring the realms affected by this, and use the data we gather to implement further optimisations. Our ultimate goal is to work toward the removal of the limit.
Forum Avatar
Eutheos
#1 - Feb. 19, 2009, 9:54 a.m.
Blizzard Post
So this explains the reason for that annoying message. Well thanks for the heads up!

I certainly hope that you'll be able to find a better way of managing the instance problems than the artificial instance numbers cap. This seems like a crude way of fixing what is, based on your earlier reports on problems with Lake Wintergrasp, essentially a problem with the code optimization... Sorry that it had to come down to such solutions :/

EDIT: Look, first!
Forum Avatar
Thundgot
#30 - Feb. 19, 2009, 6:02 p.m.
Blizzard Post
Q u o t e:
so now at peak times we will have to wait even longer to get into an instance, coz before this 'fix' was put in place we already got the error 'Additional instances could not be launched' a lot of the time

It seems a little clarification is in order.

This was not implemented just now. It's been in for quite some time, but we wanted to share some explanation on the matter and also assure you we are continually working on optimisations and that the goal is definitely to remove the limit.