7 ms·
Kids today don't remember needing a purchase order to buy hardware that had to be shipped, racked and configured. Adding scale went from 6 weeks to 6 seconds.
by tootie 10y ago
Kids today don't remember needing a purchase order to buy hardware that had to be shipped, racked and configured. Adding scale went from 6 weeks to 6 seconds.
- toomuchtodo 10y agoThe vast majority of business do not need to scale on a dime. You're paying 30-40% more to provision in 6 seconds in AWS (and let's be real, it's low 5 minutes at least for most resources like instances), but if you've got the cash to waste, go for it. As always, marketing is key.
- derefr 10y ago> and let's be real, it's low 5 minutes at least for most resources like instances If you've got a pre-baked application AMI, are using EBS-backed instances, and are starting them with auto-scaling or health-checks rather than manually using the console, then no, you really can have new instances up in a couple of seconds. Mind you, the key (to getting a high ROI from AWS) isn't scaling up on a dime. It's scaling down on a dime, whenever your load decreases for even a minute or two, knowing you can just scale right back up. Being able to run with literally no paid compute-hours spent sitting around doing nothing waiting for a task can save you a rather large amount of money, usually quite easily compensating for that 30-40% AWS surcharge.
- toomuchtodo 10y agoI'd love if you could point the way then, because my pre baked AMIs that are EBS backed are always taking at least 3-5 minutes to be healthy and processing traffic or requests from the moment they're spun up. This is not restricted to a specific instance type, nor a specific region. There is literally no way you are performing compute in seconds from when an EC2 instance is instaniated. I've bookmarked this to come back to benchmark this.
- aquark 10y ago> whenever your load decreases for even a minute or two, knowing you can just scale right back up. Doesn't AWS still charge by the hour ... so if you were spinning instances up and down based on minute-to-minute load you would be overpaying for vs just maintaining a steady baseline. If you turn an instance off you need to be pretty confident it will stay off for at least an hour.
- Alain-lf 10y agoAWS charge by the hour, as soon as you power up an instance you are charged a full hour. If you start and stop one instance 60 time in an hour, you will be charged 60 hours. So scaling down on a dime and scalling right back up is more expensive than doing nothing.
- toomuchtodo 10y agoBingo. If you've scaled up, you stay scaled up for the instance hour. Otherwise, you just threw money away.
- brianwawok 10y agoGCE only need 10 minutes and then you can spin down.
- flippy2 10y agoThat's not at all true. You would be charged for exactly one hour. Instance hours are just rounded up. Source: I auto scale my companies entire stack.
- Alain-lf 10y agoAmazon and people who have been hit by this seem to disagree with you: "Pricing is per instance-hour consumed for each instance, from the time an instance is launched until it is terminated or stopped. Each partial instance-hour consumed will be billed as a full hour." https://aws.amazon.com/ec2/pricing/ https://aws.amazon.com/ec2/pricing/ "You are billed for an EC2 instance-hour for each hour or partial hour (rounded up) that your instance is in the “running” state. Instances that are in any other state (“stopped”, “pending”, etc.) are not billed." https://aws.amazon.com/premiumsupport/knowledge-center/ec2-instance-hour-billing/ https://aws.amazon.com/premiumsupport/knowledge-center/ec2-i... Here's a company that got hit hard by that behavior : "A little-discussed fact about AWS EC2 pricing is that users are billed for each server that runs for any partial hour it runs. That means if a user starts a server and then kills it within five minutes, he is still billed for the full hour. That seems acceptable, but if a user kills a server and replaces it with a new server of the exact same type and location, this move doubles the bill." http://searchaws.techtarget.com/tip/Paying-the-price-when-an-AWS-Auto-Scaling-group-runs-amok http://searchaws.techtarget.com/tip/Paying-the-price-when-an... You should probably take a look at this, you are probably costing your company a lot of money.
- mnutt 10y agoWould it make sense to spin up a bunch of instances and then stop them, then manage your own autoscaling by just starting/stopping rather than launching/terminating? What's the downside there? You only pay for EBS storage, which is a tiny fraction of compute costs.
- la6470 10y agoDepending on usage pattern also consider reserved instances where you pay deeply discounted upfront price for your instances OR/AND spot instances where you bid for computing power for instances that are suitable for transient loads and doesn't matter if they get terminated suddenly. The good this is that RIs and SIs are integrated with other services like EMR Amazon map reduce or ECS ec2 container service.
- jghn 10y agoThere comes a time where it is way cheaper to not deal with your own IT. My company has a many thousand core cluster with ~30PB of storage on prem. We finally decided that maintaining that ourselves was nuts, and while it's expensive as hell to pay our cloud provider it ends up being cheaper in the long run for multiple reasons
- jerkstate 10y agoThat's completely nuts - for 30PB you'll be paying like $1.5M per month for storage and compute, you could buy all the hardware for maybe $3-5M and rent space for it for like $50k per month.. over 3 years the same cluster would cost you over $50M on AWS versus $10M to do it yourself (let's be generous and say plus 10 engineers at $2.5m/year to run it) so $17.5M to DIY.. there are some situations where it makes sense, like if your baseline is low and your fluctuation is high, but IMO if you have a baseline of 30PB, you'd be able to pay for a lot more engineers if it was in house.
- jghn 10y agoWe haven't fully transferred yet, but yes our monthly bills are quite large. From everything i've heard it's been a net savings. There are other advantages such as the cheaper 'deep storage' tiers, spinning up just the compute we need it on demand instead of having to worry about keeping it all packed, etc. It's going to be expensive and a pain in the ass either way. Our largest problem has been the realization that "the cloud" is not in fact infinite despite what the the commercials will have you believe. We quite frequently are told to cool our jets.
- tw04 10y agoYou can get those same "deep storage" tiers on prem for a fraction of the cost of AWS. There's no scenario, short you of you running the systems at less than 40% capacity, that AWS is cheaper. You have to be criminally inefficient or very very very small (like less than one server small) for AWS to EVER be a cost play. I should add, bursty workloads like batch processing can be a cost play simply because a once-a-month even that is time sensitive can benefit greatly from instant* CPU that you don't have to pay for the rest of the month. Those workloads tend to be very niche and one-off for most businesses though.
- saryant 10y ago...
- chrissnell 10y agoThis is rapidly changing. When I took over technical ops at my employer, we were 100% public cloud. I quickly moved us to private managed cloud and quadruped our capacity for 20% less spend. Now I'm in the process of preparing us to move to colocation, where I'm certain that I can save another 40-50% over three years. What's made this possible is technologies like CoreOS, Kubernetes, and Ceph. We are working on automating the bare metal network management pieces but I am confident that we will soon have an environment that can function in colo without onsite staff. If we automate throughly and pre-cable racks, adding capacity is as simple as using a colo provider's remote hands service to rack and stack new hardware every quarter or so.
- learningman 10y agoSerious question, what are you doing better compared to AWS? Efficiency wise, what can't you offer your own cloud services and cash in on 40-50% markup?
- toomuchtodo 10y agoRunning a single tenant cloud system is not the same as a multi tenant cloud system.
- ec109685 10y agoWhat happens if that Colo goes down?
- toomuchtodo 10y agoYou wait for it to come back, just like when us-east-1 is having problems every few weeks.
- chrissnell 10y ago
- fabian2k 10y agoWhen I looked last AWS EC2 isn't just 30-40% more expensive than renting a dedicated server, but up to 5-10x as expensive. And if you're using a lot of outgoing traffic, AWS gets even worse in comparison.
- tootie 10y agoIt's not even just scaling. Even just getting our dev, as and CI servers started on day 1 is a huge plus.
- acdha 10y agoIt's not just scaling - a lot of the value comes from how you can change your practices to be more reliable: e.g. instead of having the classic model where you get servers setup and run them for years, now every application no matter the scale or how mature uses APIs to interact with your infrastructure, has automated blue-green deployments, every developer (or your CI process) can spin up instances to test in a production-like environment, you have things like RDS/ELB/S3/etc. as turn-key services which anyone can take for granted when designing their application, everything can be secured with limited scope API keys / policies, etc. When you suddenly get a spike in demand (annual reporting, unanticipated new work, one-time migration / reprocessing, etc.) you can have everything you need instantly without a large procurement lead-time or having to either repurpose existing infrastructure or find a use for new hardware for the rest of its service lifetime. Absolutely all of that _could_ be done in a traditional IT environment but it's rare to see it done at the level of usability that AWS (or Azure, Google, etc.) offers and that leads to cost both in staff time, technical debt, and time-to-recover after failures. You definitely can beat AWS on pricing but it requires both sufficient scale and ongoing commitment to spend staff time developing and supporting infrastructure, which is usually an area where organizations choose to skimp.
- gaius 10y ago5 minutes at least for most resources like instances As of this evening, in eu-west-1 it's about 70 seconds.
- jabzd 10y agoWe're in the healthcare space so we have to own our hardware and co-locate. Being a small outfit, sometimes it's so frustrating trying to find the right resources online these days related to racking and configuring your own bare metal! I can definitely appreciate the 6 weeks to 6 seconds. We recently added a new database server because we were really struggling at peak times. The 5 weeks it took between ordering the $25k server, configuring base os, racking it, replicating current data to it, and then choreographing the switch was brutal. Due to the nature of our product, it had to be a zero-downtime switch. Somedays, I wish it was as simple as clicking upgrade instance on AWS RDS. Other days, I make myself feel better by calculating the thousands I'm saving a month.
- jghn 10y agoWhy is it "have to own", HIPAA? I know that both HIPAA and CLIA have issues with things like the spot market but you can still be approved via cloud.
- jabzd 10y agoNot so much HIPAA directly, but the business associate agreements that many customers make use of. In order to meet the requirements of many of the agreements we have in place, we have to own any and all hardware that PHI data lives on. They don't exactly accept redlines on those kinds of agreements.
- deleted 10y ago[deleted]
- ceejayoz 10y ago> We're in the healthcare space so we have to own our hardware and co-locate. https://aws.amazon.com/compliance/hipaa-compliance/ https://aws.amazon.com/compliance/hipaa-compliance/
- jabzd 10y agoUnfortunately, many standard business associate agreements with clients have yet to catch up to cloud offerings having better compliance guarantees. Many of our agreements with customers, both more recent and legacy, are the reason for the requirement.
- gaius 10y agoI know right. One company I worked for it would take literally 6 months for the internal IT organization to provision a VM and configure it to the state that it was actually usable, and they would chargeback hundreds of dollars a month for it. Physical/dedicated hardware you would need to set the wheels in motion 12-18 months in advance of when you needed it. That IT department, I still know people there, is currently flailing desperately for a solution to the problem of the business having discovered how quick it is to provision on AWS and what it costs there, even tho' it "looks" expensive it is still a massive saving compared to the fully loaded cost of many large company's IT departments. And even if it takes an hour to spin up an instance, that is still an unbelievable miracle to people who were used to the old way. Questions are being asked for which there are no easy answers...
- rblatz 10y agoI've experienced that first hand. I was told it would take 3 weeks to setup and provision a VM that had IIS installed. This was a Microsoft shop, so one would assume the massive VMWare cluster they ran had dozens of instances like that. The guys in IT couldn't understand why the devs and the rest of the business were rapidly moving to Azure...