As someone working in IT, I can't believe you'd make such a newbie mistake. IO parallelism is not the only factor involved in this sort of rollout, and you know it. You have to imagine that there's more to the process than 'image and go.' Wow's a complex system, the servers no doubt operate in clusters, the 'single database server' per battlegroup is almost guaranteed to be clustered. With the sheer number of points of failure that must be involved, not to mention the fact that there's not a 'standard' hardware configuration (newer realms have newer hardware) you can be damn sure there's most likely a tedious, thorough automated smoke test of every facet of connectivity and performance, not to mention multiple failures per rollout requiring engineering attention. This is completely ASIDE from the fact that they're generally not keen on bringing down servers for extended maintenance all that frequently and so more complex hardware upgrades, growing of RAID volumes and other longer-term tasks are PROBABLY on their schedule for these patch rollouts when they have more leeway (people don't expect the average tuesday downtime to run over, patch days it's a known fact of life.)
I mean, seriously. You're acting like this is a fire and forget operation.
"The vulnerability allows remote attackers to cause a denial of service crash and execute a code to take control of your system by delivering this malicious code through a specially crafted PDF or Flash file. "
Clearly, this article was not written by someone with any real grasp on how computers work.
Well, this is kinda retarded. You pretty much have the best wow-related domain name and you're shuttling off to... what - a subdomain at Joystiq? Literally, worst idea ever. Good luck with it, but AOL, ffs, get your head out your ass, your inability to realize value when you have it is what made you a third-rate joke on the internet to begin with.
Yeah, man, when the rest of us software engineers write software on deadlines we turn out 100% bug-free code all the time, Blizzard's just unique in that they make mistakes in their unprecedentedly massive project.
I really, really hate DPS who can't stand to wait 30-45 seconds here or there for regrouping or just slight RL distractions (or buffs.) Just because you think you're too good for heroics doesn't mean there aren't four other people in the group and when I'm running around cleaning up your mess because you lost a mob and now it's wailing on the healer because you pulled while I was low on mana from buffing? That makes me pissed.
Ironically, there's a high correlation between DPS who are impatient and my inability to taunt off of them.
You have to have all the expansions before any expansion to install it. You need BC installed to install wrath, you'll need BC and Wrath to install Cataclysm. If you didn't install them, you'd have keys to play through the level 1-60 content, and then the 80-85 content, but no way to actually get from 60-80. Therefore the expansions before are a pre-requisite.
@mutak It's a carryover from UNIX. The format for UNIX time was standardized in 1972, and they figured that starting the clock at the beginning of the decade seemed reasonable.
@lynkfox - You're looking at it wrong. On a per-attempt basis there is no increase in probability. When you run once, the chance that the next run will drop the item is the same as the chance before.
When you're looking at a set of 100 runs however, the probability that that set of 100 runs contains the drop somewhere is significantly larger. On an instance-by-instance basis however the probability does not change.
Maintenance extended: 5:00 p.m. PST
Nov 23rd 2010 4:27PM (WoW)As someone working in IT, I can't believe you'd make such a newbie mistake. IO parallelism is not the only factor involved in this sort of rollout, and you know it. You have to imagine that there's more to the process than 'image and go.' Wow's a complex system, the servers no doubt operate in clusters, the 'single database server' per battlegroup is almost guaranteed to be clustered. With the sheer number of points of failure that must be involved, not to mention the fact that there's not a 'standard' hardware configuration (newer realms have newer hardware) you can be damn sure there's most likely a tedious, thorough automated smoke test of every facet of connectivity and performance, not to mention multiple failures per rollout requiring engineering attention. This is completely ASIDE from the fact that they're generally not keen on bringing down servers for extended maintenance all that frequently and so more complex hardware upgrades, growing of RAID volumes and other longer-term tasks are PROBABLY on their schedule for these patch rollouts when they have more leeway (people don't expect the average tuesday downtime to run over, patch days it's a known fact of life.)
I mean, seriously. You're acting like this is a fire and forget operation.
Adobe announces new Flash security vulnerability
Sep 17th 2010 1:12PM (WoW)Adobe announces new Flash security vulnerability
Sep 17th 2010 12:36PM (WoW)Clearly, this article was not written by someone with any real grasp on how computers work.
WoW.com is moving to wow.joystiq.com
Sep 16th 2010 10:08AM (WoW)Patch 3.3.5 known issues
Jun 22nd 2010 7:22PM (WoW)The Lawbringer: Gold sellers are criminals!
Apr 6th 2010 7:52AM (WoW)Breafast Topic: Do you use all available buffs when pugging?
Mar 18th 2010 9:26AM (WoW)Ironically, there's a high correlation between DPS who are impatient and my inability to taunt off of them.
The Queue: Not quite mutual destruction
Jan 14th 2010 1:51PM (WoW)Drop chance probability
Jan 14th 2010 8:36AM (WoW)Drop chance probability
Jan 13th 2010 11:26AM (WoW)When you're looking at a set of 100 runs however, the probability that that set of 100 runs contains the drop somewhere is significantly larger. On an instance-by-instance basis however the probability does not change.