this is the way to fix server problems!
WTF!
us server queue 332 , after an hour waiting 132!
switch to asia 776 !
this is insane way to make something reasonable !
this time you really missed up!
I’ve already stated my rebuttal in a previous post, one that you so seem not to understand. :’)
Even if you get past the queue right now you will be DC’d every 5-10 min.
How many players vs how many bots in the queue? I guess it must be more players because it’s not this bad other days
If that’s true, then the architecture and design team is lousy … Couldn’t they have changed the backend? How do they think of reusing a code from 20 years ago?
I just had Sandstorm Treks drop for my amazon. My laptop was getitng really hot so i logged out. Logged in to 298 in queue. Waited, it stayed the same.
Nothing.
Relogged. Queue is 350. Relogged again. Queue is 425. Okay, so it’s just backing up and noone can get in. Fine. But I swear, if those sandstorm treks are gone, I’m demanding a refund. ive other valuable rare items that i haven’t gotten again since rollbacks, not dealing with that again.
1 Like
As you can imagine, that’s a big task for one database, and wouldn’t cope on its own. So to alleviate load and latency on our global database, each region–NA, EU, and Asia–has individual databases that also store your character’s information and progress, and your region’s database will periodically write to the global one.
…
On Saturday morning Pacific time, we suffered a global outage due to a sudden, significant surge in traffic. This was a new threshold that our servers had not experienced at all, not even at launch.
…
these two factors combined overloaded our global database, causing it to time out.
…
we saw an even higher increase in traffic, causing us to hit another outage.
…
Then Tuesday, we hit another concurrent player high, with a few hundreds of thousands of players in one region alone. This made us hit another incident of degraded database performance
…
So what are the TWO factors mentioned here?!
They wouldn’t be database issues AND legacy code, would they?
And everyone knows its not a traffic thing, its a competence issue.
You disingenuous prick.
This is what we get for not pushing them to give EU & Asia their own “global database” we wouldnt be in this position at all and they could spent 10 freaking minutes to try and stop the constant client crashes.
I’ve been waiting 40 minutes and still at 338 where I started
I think people are adapting and just staying in game so the queue never moves.
During peak times the game needs to aggressively time out inactive people
1 Like
It’s both, you insufferable moron.
They can simultaneously update their code and invest in more and better hardware.
The server outages are caused by problems when they hit concurrent traffic numbers that exceed thresholds but sure, it’s not a traffic problem.
You would think they know how many people they sold the effing game to
1 Like
And do things like logging out idle players rather than let you afk in game for 8 hours straight while people can’t get in.
This kind of stuff happens sadly though. Maybe blizzard saw this game having a smaller player base and kept legacy code then. Now they find out they had some predictions wrong. Your not always right
They kept legacy code because they couldn’t remake a 20 year old game from scratch to save their company. They didn’t even have to come up with new ideas, they just had to translate the old code into something more suited to modern architecture. I can see no reason why they wouldn’t other than they simply can’t (be it money or talent or both). And if they couldn’t do it for release, what hope is there that they will ever get it right?
Just dropped to 312! Never thought I would be this excited about moving up 100 spots in a 400+ queue… smh. lol
Ive been waiting for about 30 and my number hasn’t changed at all…
Hey fanboy to be fair YOU dont have a CLUE what the problem is. You repost some BS about legacy code from someone else. You have no idea what you are talking about. Just knock it off kiddo.
Down to 41 now from 382 at 10am.