GPU instances for $0.65 an hour. Wow!
It's the old price - no discount for g2 instances ;(
It's been a while since I looked, but I recall GPU prices being around $2 and hour (and thus writing them off).
Amazon EC2 Pricing Changes Effective April 1, 2014
141–150 of 151 posts
Re: Amazon EC2 Pricing Changes Effective April 1, 2014
#142Earlier quoted context omitted.
DO is great for hacking on personal projects. I prefer AWS for work stuff because firewall, security groups and networking are much easier to manage. I have not yet tried GCE but I may move some of my dev stuff over once they roll out the private git repos.
The private git repos rolled out a while ago. https://source.developers.google.com/p/PROJECT/r/default You might have to turn it on in your developer console, not sure. At the moment, pushing to its "master" branch tries to deploy to app engine, so that might not be what you're looking for. You can clone it (and, in the future, your connected repos and other Google-hosted repos) with 'gcloud init PROJECT', and things…
Can you use this as a replacement for Github private repos?
Re: Amazon EC2 Pricing Changes Effective April 1, 2014
#143Earlier quoted context omitted.
It's the old price - no discount for g2 instances ;(
It's been a while since I looked, but I recall GPU prices being around $2 and hour (and thus writing them off).
$2 per hour are cluster compute instances with 2 NVIDIA Tesla M2050 GPUs (“Fermi” GF100) GPUs.
g2 instances are smaller with NVIDIA GRID GPUs (“Kepler” GK104).
- G2 popular use cases: Game streaming, 3D application streaming, and other server-side graphics workloads.
- CG1 popular use cases: Computational chemistry, rendering, financial modeling, and engineering design.
Re: Amazon EC2 Pricing Changes Effective April 1, 2014
#144I just reserved a series of heavy-utilization m3.xlarge instances for roughly $30k. Apparently, if I had waited a month, I could have saved about $13k because of these price reductions. I can't help but feel that I got really fucked by poor timing that I couldn't control. It would hurt so much less if these price changes were more gradual and somewhat consistent (perhaps monthly).
It's worth calling and talking to your sales rep about this. I've found AWS to be surprisingly accommodating with pricing.
Shouldn’t such cases be detected automatically? It would really help Amazon’s brand of being shroud.
Re: Amazon EC2 Pricing Changes Effective April 1, 2014
#145Earlier quoted context omitted.
The private git repos rolled out a while ago. https://source.developers.google.com/p/PROJECT/r/default You might have to turn it on in your developer console, not sure. At the moment, pushing to its "master" branch tries to deploy to app engine, so that might not be what you're looking for. You can clone it (and, in the future, your connected repos and other Google-hosted repos) with 'gcloud init PROJECT', and things…
Can you use this as a replacement for Github private repos?
It really depends on what you mean. It is a private git repo, so in that sense yes.
Re: Amazon EC2 Pricing Changes Effective April 1, 2014
#146Your move, Microsoft Azure.
Re: Amazon EC2 Pricing Changes Effective April 1, 2014
#147I would be so happy if Heroku passed along these price cuts to their customers, but based on past AWS price cuts, I'm not holding my breath.
Heroku hasn't changed pricing since they launched, actually. The only historical price reference I quickly found was that the EC2 was $0.085/hr for (what is now called) an m1.small[1]. Heroku launched with $0.05/hr pricing. Amazon's new m1.small pricing is $0.044/hr, nearly a 50% price drop over four years. Heroku still is $0.05/hr, the same price as when it launched. Heroku runs on EC2. [1] http://www.sunsetlakesoft…
Uh, did I miss something here? Sounds like Heroku was actually cheaper than the raw EC2 rate when it launched, and is now just over half a cent per hour more.
Re: Amazon EC2 Pricing Changes Effective April 1, 2014
#148Earlier quoted context omitted.
Heroku hasn't changed pricing since they launched, actually. The only historical price reference I quickly found was that the EC2 was $0.085/hr for (what is now called) an m1.small[1]. Heroku launched with $0.05/hr pricing. Amazon's new m1.small pricing is $0.044/hr, nearly a 50% price drop over four years. Heroku still is $0.05/hr, the same price as when it launched. Heroku runs on EC2. [1] http://www.sunsetlakesoft…
Uh, did I miss something here? Sounds like Heroku was actually cheaper than the raw EC2 rate when it launched, and is now just over half a cent per hour more.
Heroku prices are per "dyno" which are significantly less powerful than an EC2 small.
Re: Amazon EC2 Pricing Changes Effective April 1, 2014
#149I just reserved a series of heavy-utilization m3.xlarge instances for roughly $30k. Apparently, if I had waited a month, I could have saved about $13k because of these price reductions. I can't help but feel that I got really fucked by poor timing that I couldn't control. It would hurt so much less if these price changes were more gradual and somewhat consistent (perhaps monthly).
Well, I bought a 3-year reserved heavy utilization plan just a couple of hours before these news went live. My pain is about 2 orders of magnitude less than yours, though. I wonder if you can contact someone at Amazon and ask for some kind of discount. Anyway, what a massive drop in price and what a swift reaction from Amazon. Competition can really do wonders. I just hope we won't be seeing drops in the level of ser…
Knowing amazons customer service, I would be floored if they would refund you the difference. A couple weeks/days? Maybe maybe not, depends on which rep you get honestly. But a couple hours? That would just be cruel for them not to.
Re: Amazon EC2 Pricing Changes Effective April 1, 2014
#150Earlier quoted context omitted.
We use RDS (they now support Postgres) and Elasticache. The pricing seems reasonable for the performance (I've not done benchmarks if I'm being honest), and you get to treat all your EC2 instances as expendable.
If you're eschewing EBS because of past problems (like the Oct 2012 outage), you should be aware that RDS is EBS-backed [1]. Also, on EC2, EBS-backed instances boot faster [2]. Of course, you can (and should) still treat EBS-backed instances as expendable. [1] http://aws.amazon.com/rds/faqs/#hardware-scaling [2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Component...
Just to clarify: I don't eschew RDS because of outage issues, I use RDS because it's much easier to set up and manage compared to doing it yourself.
To be honest, I didn't know RDS was backed by EBS but it makes little real difference to me as long as the backup procedures are rock-solid and the performance is acceptable.