Skip to Content
12-23-2008 @ 11:53AM
And what it all boils down to is that Blizzard could easily just add more server power to the instance server cluster and SOLVE this problem, but I'd think they are too busy counting their money.I mean.. a week or 2 of this is all fine and unexpected. but they are obviously doing nothing about it which sucks.
12-23-2008 @ 12:04PM
If you think Blizzard is doing nothing about it because it's taking a few weeks to clear it up, you're a damn fool. You can't just throw more hardware into the mix and expect it to clear things up.It's a big game. Bigger than anything out there. Blizzard is doing something effectively unknown to any other company in the history of gaming. The scale is immense. It's a truly unique problem that they're working on solving every day.Don't be a moron. If it bothers you that much, cancel your account. The other 12 million of us will enjoy our game and realize that the occasional glitch is just part of the experience.
12-23-2008 @ 12:05PM
Right, because we haven't had 3 weeks of blue posts about this particular issue or anything.I doubt you'll be getting the apparently non-existent fix soon anyway, or did you not notice its the christmas holidays?
12-23-2008 @ 12:19PM
Any server/network admin who knows what they are doing knows that blindly throwing more capacity/power is never the answer.
12-23-2008 @ 12:13PM
It's really not that easy. Introducing new architecture into a server environment always makes things more complicated and prone to problems. It's not like they can just slot in a few more RAM chips like you do at home, these servers are probably already maxed out on everything so upgrading them would require replacing entire machines, which takes a LOT of testing and planning not to mention more downtime than usual.Blizzard knows what they're doing, so how about we stop thinking we know better than one of the most profitable game companies in the world.
12-23-2008 @ 1:47PM
You can't just spend money and have that solve IT problems.Testing alone takes weeks.
12-23-2008 @ 1:01PM
Well, to be honest, if this was coded properly in the first place to allow for scalability then it shouldn't be too hard to add another server. If a server reaches it max, have the server return an error code, if that error code is received attempt a different server in the list of "instance servers". My guess is that it wasn't coded like this and they are probably recoding as we speak. Of course, they could just be sitting back and counting their money. Honestly, with well over $200 million in recurring revenue I'm sure they could find a way to fix the problem. My theory is that they want you to be unhappy with your high pop server and to transfer to a medium pop server. After I transferred I haven't had another queue time and never had any instance zoning or world server down problems. Of course, there is a great lack of "talent" on the med pop servers. But that just takes some training. :)
12-23-2008 @ 2:20PM
Anyone else notice there is always a correlation between people assuming the MALEVOLENCE of Blizzard and the OMNISCIENCE of Blizzard?"Blizzard can do anything, but they choose not to because they are (1) too busy counting their monies to notice us, or (2) they want to screw with us."Any time anyone starts falling into the trap of believing crazy, kooky conspiracy theories like this its a sign you're taking this company too seriously. Go outside. Read a book. There's a whole world out there that ISN'T conspiring to make your life miserable.
12-23-2008 @ 3:10PM
Blizz needs to stop playing in their money vault and (buy more servers!!! / hire more technicians!!! / write better code!!!)I am a (web developer / VB programmer / IT field unrelated to server cluster admin) so trust me, I know what I am talking about. If Blizz did things the way *I* suggested, they wouldn't be dealing with (major content patch launch glitches / minor instance issues / bugged quest rewards).
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.