As a Californian, I would like to see the subsidies for farming stop in this state. Did you know we grow rice in California? Freaking rice, which requires copious amounts of water. Why?
Because the state government has subsidized farming irrigation so they only pay 1% of what the rest of us pay for water. If certain types of agriculture are water intensive they should be grown in regions of the country that is geared for that, not a state that is predominantly considered dry. The truth of the matter is that California farming consumes 80% of our water supply. (http://www.arb.ca.gov/fuels/lcfs/workgroups/lcfssustain/hanson.pdf) It's the Pareto principle in full effect, to the detriment of the non-farming portions of the state.
The end result is that we have drought after drought and major calls to conserve. The funny thing is if the same government that was calling us to conserve wouldn't spend taxpayer dollars subsidizing types of agriculture that wouldn't naturally grow here anyway, then we wouldn't be in this mess to begin with. Le sigh.
As a developer, it really disheartens me to think that any application I create that becomes popular is likely to be litigated against for patent violations. I've never searched for patents or seen one and thought "AHA! That's how I'll make this algorithm!" No, I just code and create logical solutions to problems that are presented.
No one should be able to claim ownership of the fact that 2 + 2 = 4 and force others to always use 3 and 1 to do addition for the next 20 years. God forbid, someone patents 3 + 1 = 4!!!
The article said each instance had 7GB of memory and 8 cores. That would translate to the High-CPU Extra Large Instance Type:
High-CPU Extra Large Instance 7 GB of memory, 20 EC2 Compute Units (8 virtual cores with 2.5 EC2 Compute Units each), 1690 GB of local instance storage, 64-bit platform Source: http://aws.amazon.com/ec2/
That instance type will run you $0.68/hour standard or $0.24/hour spot. (US-East Pricing) (Spot pricing allows you to take advantage of unused EC2 instances at a discount. Also worth noting is that spot pricing changes over time.)
30,000 cores equates to 3,750 instances across different regions. Here is the breakdown on hourly pricing for standard and spot. (Reality is it was probably a mixture of both and the pricing for different regions varies).
Standard US-East: $2,550/hour Spot US-East: $900/hour
The exact mix of machines in each region wasn't specified but $1,279/hour sounds about right if there is a mix of standard vs spot across different regions.
Nail on the head here. We were affected today and while I have full offsite backups of everything we don't have a second datacenter to switch on because of cost and complexity. It's not too difficult to have webservers span different parts of the globe, but DB servers like MySQL are a whole different story and usually very crucial.
Ok, I work with both as the CTO of an internet advertising firm. We spend in the 6 figures a month with both MSN/Bing/Binghoo/whatever and Google. I would rather work with Google any single day of the week. Dealing with MSN behind the scenes is like trying to teach Japanese to my dog. He may be able to respond to a few commands with immense repetition, but he never really gets the big picture of what I am trying to communicate. Don't even get me started on how painful it is to work with the MSN API vs Google's.
Slashdot Mirror
As a Californian, I would like to see the subsidies for farming stop in this state. Did you know we grow rice in California? Freaking rice, which requires copious amounts of water. Why?
Because the state government has subsidized farming irrigation so they only pay 1% of what the rest of us pay for water. If certain types of agriculture are water intensive they should be grown in regions of the country that is geared for that, not a state that is predominantly considered dry. The truth of the matter is that California farming consumes 80% of our water supply. (http://www.arb.ca.gov/fuels/lcfs/workgroups/lcfssustain/hanson.pdf) It's the Pareto principle in full effect, to the detriment of the non-farming portions of the state.
The end result is that we have drought after drought and major calls to conserve. The funny thing is if the same government that was calling us to conserve wouldn't spend taxpayer dollars subsidizing types of agriculture that wouldn't naturally grow here anyway, then we wouldn't be in this mess to begin with. Le sigh.
As a developer, it really disheartens me to think that any application I create that becomes popular is likely to be litigated against for patent violations. I've never searched for patents or seen one and thought "AHA! That's how I'll make this algorithm!" No, I just code and create logical solutions to problems that are presented.
No one should be able to claim ownership of the fact that 2 + 2 = 4 and force others to always use 3 and 1 to do addition for the next 20 years. God forbid, someone patents 3 + 1 = 4!!!
It's about time someone charged Microsoft for all the wasted time and resources spent fixing websites for Internet Explorer!
The article said each instance had 7GB of memory and 8 cores. That would translate to the High-CPU Extra Large Instance Type:
High-CPU Extra Large Instance 7 GB of memory, 20 EC2 Compute Units (8 virtual cores with 2.5 EC2 Compute Units each), 1690 GB of local instance storage, 64-bit platform
Source: http://aws.amazon.com/ec2/
That instance type will run you $0.68/hour standard or $0.24/hour spot. (US-East Pricing) (Spot pricing allows you to take advantage of unused EC2 instances at a discount. Also worth noting is that spot pricing changes over time.)
30,000 cores equates to 3,750 instances across different regions. Here is the breakdown on hourly pricing for standard and spot. (Reality is it was probably a mixture of both and the pricing for different regions varies).
Standard US-East: $2,550/hour
Spot US-East: $900/hour
The exact mix of machines in each region wasn't specified but $1,279/hour sounds about right if there is a mix of standard vs spot across different regions.
Nail on the head here. We were affected today and while I have full offsite backups of everything we don't have a second datacenter to switch on because of cost and complexity. It's not too difficult to have webservers span different parts of the globe, but DB servers like MySQL are a whole different story and usually very crucial.
Ok, I work with both as the CTO of an internet advertising firm. We spend in the 6 figures a month with both MSN/Bing/Binghoo/whatever and Google. I would rather work with Google any single day of the week. Dealing with MSN behind the scenes is like trying to teach Japanese to my dog. He may be able to respond to a few commands with immense repetition, but he never really gets the big picture of what I am trying to communicate. Don't even get me started on how painful it is to work with the MSN API vs Google's.
Well put. Ditto for us over here.