It amazes me that a company like Blizzard with a title as anticipated as Diablo 3 cannot get a release even close to working properly. They told us to expect Error 37 and queue's. Ok how about you (blizz) expect the millions of pre-orders to try to log on when you release your product. I really don't get how you can fairly accurately predict the numbers of people logging in and not have the infrastructure to handle it. It makes 0 sense. Huge dropping of the ball IMO.
Anyone with any experience handling infrastructure for this type of thing have insights to share? Would appreciate it so I'm not completely dumfounded.
Don't get me wrong I'm still Crtl-V/enter ing like the rest of you. And im going to play the shit outa this game. But really............
I'm sure they would have to make an incredibly massively huge investment in servers and bandwidth to support the number of people all trying to log in during the first few hours. But when things calm down the next day, they wouldn't need it anymore and would have tons of useless equipment just sitting around. It's pure economics.
With all of the experience from previous releases It would be hard to convince me that they don't have experience handling millions of simultaneous log in attempts. They absolutely knew what to expect and failed to create a system to handle it.
It amazes me that a company like Blizzard with a title as anticipated as Diablo 3 cannot get a release even close to working properly. They told us to expect Error 37 and queue's. Ok how about you (blizz) expect the millions of pre-orders to try to log on when you release your product. I really don't get how you can fairly accurately predict the numbers of people logging in and not have the infrastructure to handle it. It makes 0 sense. Huge dropping of the ball IMO.
Anyone with any experience handling infrastructure for this type of thing have insights to share? Would appreciate it so I'm not completely dumfounded.
Don't get me wrong I'm still Crtl-V/enter ing like the rest of you. And im going to play the shit outa this game. But really............
Honestly, this is a bigger game launch then Cata was, there is literally no precedent for this kind of a server hit.
Most MMO games have big hits at launch, and they usually have a few hours of issues, and they have FAR less people to deal with.
It sucks, dont get me wrong, im not sure how many players are actually getting in, as opposed to those unable to.
With all of the experience from previous releases It would be hard to convince me that they don't have experience handling millions of simultaneous log in attempts. They absolutely knew what to expect and failed to create a system to handle it.
They DO have experience. They let everyone at once crash their servers, and when the logins die down a little the game starts to run smooth. There's nothing they could do ATM save for having spent a ton of money on equipment they wouldn't need the next day (as said above).
I'm sure they would have to make an incredibly massively huge investment in servers and bandwidth to support the number of people all trying to log in during the first few hours. But when things calm down the next day, they wouldn't need it anymore and would have tons of useless equipment just sitting around. It's pure economics.
^ This is exactly what I was going to post. There is no reason they would spend all that money to be able to handle 1 million+ people simultaneously logging on when 24 hours after release the most they can expect is a few thousand, maybe tens of thousands during peak times.
They HAVE learned... that's why the servers haven't (yet) completely gone to hell and just crashed. They are throttling the number of people that can log in at a time, so that those who ARE connected don't get kicked out and end up having to try and reconnect along with everyone else.
Does it suck? Sure. Is it completely avoidable? I doubt it. I would assume this is basically a denial of service attack on their servers... they have to handle it as best they can.
You have to understand that the release of Diablo 3 represents the single most massive Distributed Denial of Service attack in the history of networking. Millions (my estimate is anywhere between 1-5 million, depending on how many people are willing to stay up late in the US) of people are sending packets to the D3 login servers. Repeatedly. Constantly. For the last 75 minutes.
It's the biggest packet-bomb of all time. A packet Fat Man, if you will.
Nothing could have possibly been done to avoid it. They could have mitigated it with extra hardware, but then after this morning they'd never need 9/10 of the hardware they used to (only fractionally) mitigate the DDoS of tonight's login. That's a waste of money. They could have done X number of things to help (I'd have assigned a "login capable" time based on the B-net address on the account, not announced that until midnight, and locked changing addresses until next week unless you call customer service, to stagger the logins) but there are X number of reasons any one of those would have pissed off the community (of whiners) just as much as not being able to login is pissing them off.
Not everyone gets to go to the Super Bowl, which is once a year, and costs a lot more than D3. Not everyone gets a Mercedes Benz S-class, of which there are a limited number, and which costs far more than D3. Not everyone gets to log into D3 on the first day, but tomorrow it'll be fine.
You have to understand that the release of Diablo 3 represents the single most massive Distributed Denial of Service attack in the history of networking. Millions (my estimate is anywhere between 1-5 million, depending on how many people are willing to stay up late in the US) of people are sending packets to the D3 login servers. Repeatedly. Constantly. For the last 75 minutes.
It's the biggest packet-bomb of all time. A packet Fat Man, if you will.
Nothing could have possibly been done to avoid it. They could have mitigated it with extra hardware, but then after this morning they'd never need 9/10 of the hardware they used to (only fractionally) mitigate the DDoS of tonight's login. That's a waste of money. They could have done X number of things to help (I'd have assigned a "login capable" time based on the B-net address on the account, not announced that until midnight, and locked changing addresses until next week unless you call customer service, to stagger the logins) but there are X number of reasons any one of those would have pissed off the community (of whiners) just as much as not being able to login is pissing them off.
Not everyone gets to go to the Super Bowl, which is once a year, and costs a lot more than D3. Not everyone gets a Mercedes Benz S-class, of which there are a limited number, and which costs far more than D3. Not everyone gets to log into D3 on the first day, but tomorrow it'll be fine.
What's the problem?
I imagine if they had a queue system we would all be staring at a really big number right now and complaining about that instead.
as Zaka said its just a IP bomb you have at least 2 million people trying to log into the servers at the same time and the servers cant handle all the requests at once and the Ctrl-V spam just makes it worse cause its causing non stop activity on all servers and they cant process them. even with additional hardware it would still cause a problem.
It amazes me that a company like Blizzard with a title as anticipated as Diablo 3 cannot get a release even close to working properly. They told us to expect Error 37 and queue's. Ok how about you (blizz) expect the millions of pre-orders to try to log on when you release your product. I really don't get how you can fairly accurately predict the numbers of people logging in and not have the infrastructure to handle it. It makes 0 sense. Huge dropping of the ball IMO.
Anyone with any experience handling infrastructure for this type of thing have insights to share? Would appreciate it so I'm not completely dumfounded.
Don't get me wrong I'm still Crtl-V/enter ing like the rest of you. And im going to play the shit outa this game. But really............
Odd... i have been in and out of the game/client 15 times or more already, and i can always relog without a problem.
The first hour had problems, but i got the impression that it was smooth sailing after that, at least for everyone i have spoken to.
It amazes me that a company like Blizzard with a title as anticipated as Diablo 3 cannot get a release even close to working properly. They told us to expect Error 37 and queue's. Ok how about you (blizz) expect the millions of pre-orders to try to log on when you release your product. I really don't get how you can fairly accurately predict the numbers of people logging in and not have the infrastructure to handle it. It makes 0 sense. Huge dropping of the ball IMO.
Anyone with any experience handling infrastructure for this type of thing have insights to share? Would appreciate it so I'm not completely dumfounded.
Don't get me wrong I'm still Crtl-V/enter ing like the rest of you. And im going to play the shit outa this game. But really............
Odd... i have been in and out of the game/client 15 times or more already, and i can always relog without a problem.
The first hour had problems, but i got the impression that it was smooth sailing after that, at least for everyone i have spoken to.
Stable FPS, no dropping out of games etc..
Same - I've only logged out twice and I've been playing for 10 hours straight @.@
As for others:
Game is F***ing amazing. Stop bitching and thank god it's finally here.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Anyone with any experience handling infrastructure for this type of thing have insights to share? Would appreciate it so I'm not completely dumfounded.
Don't get me wrong I'm still Crtl-V/enter ing like the rest of you. And im going to play the shit outa this game. But really............
Honestly, this is a bigger game launch then Cata was, there is literally no precedent for this kind of a server hit.
Most MMO games have big hits at launch, and they usually have a few hours of issues, and they have FAR less people to deal with.
It sucks, dont get me wrong, im not sure how many players are actually getting in, as opposed to those unable to.
They DO have experience. They let everyone at once crash their servers, and when the logins die down a little the game starts to run smooth. There's nothing they could do ATM save for having spent a ton of money on equipment they wouldn't need the next day (as said above).
^ This is exactly what I was going to post. There is no reason they would spend all that money to be able to handle 1 million+ people simultaneously logging on when 24 hours after release the most they can expect is a few thousand, maybe tens of thousands during peak times.
Does it suck? Sure. Is it completely avoidable? I doubt it. I would assume this is basically a denial of service attack on their servers... they have to handle it as best they can.
You have to understand that the release of Diablo 3 represents the single most massive Distributed Denial of Service attack in the history of networking. Millions (my estimate is anywhere between 1-5 million, depending on how many people are willing to stay up late in the US) of people are sending packets to the D3 login servers. Repeatedly. Constantly. For the last 75 minutes.
It's the biggest packet-bomb of all time. A packet Fat Man, if you will.
Nothing could have possibly been done to avoid it. They could have mitigated it with extra hardware, but then after this morning they'd never need 9/10 of the hardware they used to (only fractionally) mitigate the DDoS of tonight's login. That's a waste of money. They could have done X number of things to help (I'd have assigned a "login capable" time based on the B-net address on the account, not announced that until midnight, and locked changing addresses until next week unless you call customer service, to stagger the logins) but there are X number of reasons any one of those would have pissed off the community (of whiners) just as much as not being able to login is pissing them off.
Not everyone gets to go to the Super Bowl, which is once a year, and costs a lot more than D3. Not everyone gets a Mercedes Benz S-class, of which there are a limited number, and which costs far more than D3. Not everyone gets to log into D3 on the first day, but tomorrow it'll be fine.
What's the problem?
I imagine if they had a queue system we would all be staring at a really big number right now and complaining about that instead.
Odd... i have been in and out of the game/client 15 times or more already, and i can always relog without a problem.
The first hour had problems, but i got the impression that it was smooth sailing after that, at least for everyone i have spoken to.
Stable FPS, no dropping out of games etc..
Same - I've only logged out twice and I've been playing for 10 hours straight @.@
As for others:
Game is F***ing amazing. Stop bitching and thank god it's finally here.