Live data from Hacker News

GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

thehftguy.com

131–140 of 179 posts

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#131
post #117

Earlier quoted context omitted.

You should have moved to bare metal months/years ago. Things like making your servers preemptible is like putting a bandaid on a gaping bullet hole.

There are many reasons why bare metal doesn't make much sense for us, at least at the moment. Here are couple: - we're very small team (13 people). We would never be able to manage this kind of infrastructure - we're growing incredibly fast. Just 6 months ago we were running on ~300 servers. We grew so quickly that we are now working with GCE's infrastructure planers to plan our resource needs - even we're not suffer…

I agree but that's years out. We are barely scratching the surface.

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#132
post #128
post #119

Earlier quoted context omitted.

I can tell you less than 1000 servers in AWS runs around 200-300k US / month I am not sure what he is doing at 25k servers but you can see real world math puts this in a serious money range. Data centers can be built for less. I wonder if the down voters on the hardware comments actually run services at scale.

What kind of servers run at that price range? I've listed [0] some of the reasons why are we hosting in cloud instead of our own datacenter. [0] https://news.ycombinator.com/item?id=13260805

Various servers, i2 for Cassandra eats most of it. Application at various levels, multi region etc etc

We too are hockey sticking but not ready to go to metal .... yet.

Your reasons make sense. I would grow that team soon :)

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#133
You should use AWS if you _really_ need something like an infinitely scalable database such as DynamoDB or some other uber-scaling AWS service that you can't replace with some open-source software on a VPS provider. 95-100% of startups don't actually need an infinitely scalable database or whatever. So they shouldn't subject themselves to Amazon's horrible pricing and throttling.

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#134
post #114

Earlier quoted context omitted.

We were sharing the same office for over a year [geekdom]. You can find my email in of the discussion chains.

Lol, sorry I failed to put 2+2 together. I can't imagine why you'd guys need 25,000 servers. Your G bill at a minimum must be over 5 million a month. I could be wrong, but those numbers don't add up too me. What instance type are you running?

We don't host on AWS, we host on GCE. Also you're way off with your estimation. We pay significantly less.

As the instance go, we have almost everything ranging from many thousands on the micro side to hundreds on the largest side.

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#135

Two points here really hit home with me about AWS (not in comparison to GCE though since I've never tried it). 1) Reserved Instances: I think the pricing model for this has become very outdated since the beginning of AWS, and it is definitely becoming cumbersome (and therefore scary) to use. 2) ELB + Traffic Spikes: I have tried (unsuccessfully) to pre-scale an ELB to prepare it for the traffic it was about to receiv…

Can you talk more about ELB + Traffic Spikes?

Under high traffic, ELB will fail?

How do you pre-scale the ELB?

Many thanks.

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#136
post #57

Looking forward to the day Google Cloud provides on-demand GPU-backed machines. Currently AWS is the only game in town for that, as far as I know.

What about N-series VMs on Azure? https://azure.microsoft.com/en-us/blog/azure-n-series-genera...

Last I checked I only found per-month pricing. Are there finer-grained options?

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#137
post #134

Earlier quoted context omitted.

Lol, sorry I failed to put 2+2 together. I can't imagine why you'd guys need 25,000 servers. Your G bill at a minimum must be over 5 million a month. I could be wrong, but those numbers don't add up too me. What instance type are you running?

We don't host on AWS, we host on GCE. Also you're way off with your estimation. We pay significantly less. As the instance go, we have almost everything ranging from many thousands on the micro side to hundreds on the largest side.

$200 a server was my estimate which is pretty conservative. I assumed that price included disk and bandwidth per server.

25,000 * $200 = 5 million a month.

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#138
post #29

I really like OVH's SoYouStart in terms of its pricing for CPU/memory intensive computations, their prices just destroy AWS/GCE: https://www.soyoustart.com/ca/en/essential-servers/

In terms of raw machine cost it generally goes owning a DC But each level down you go is another level of expertise you have to employ someone for and a loss of flexibility. The strength of the cloud has never been cost, it's always been flexibility, the ability to scale up 1000 servers in 5 minutes without any preparation or management.

You're crazy son. AWS has this thing called "Resource Limits." I'll paypal you $20 if you show me a real screenshot that show you have 1k more instances available in your resource limits than you're using - subject to hangout verification.

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#139
post #134

Earlier quoted context omitted.

Lol, sorry I failed to put 2+2 together. I can't imagine why you'd guys need 25,000 servers. Your G bill at a minimum must be over 5 million a month. I could be wrong, but those numbers don't add up too me. What instance type are you running?

We don't host on AWS, we host on GCE. Also you're way off with your estimation. We pay significantly less. As the instance go, we have almost everything ranging from many thousands on the micro side to hundreds on the largest side.

[deleted]

Re: GCE vs. AWS in 2016: Why You Shouldn't Use Amazon

#140
post #132
post #128

Earlier quoted context omitted.

What kind of servers run at that price range? I've listed [0] some of the reasons why are we hosting in cloud instead of our own datacenter. [0] https://news.ycombinator.com/item?id=13260805

Various servers, i2 for Cassandra eats most of it. Application at various levels, multi region etc etc We too are hockey sticking but not ready to go to metal .... yet. Your reasons make sense. I would grow that team soon :)

We have some large servers, but not too many of them. We're running 32 core nodes that are holding our Postgres, but the majority is smaller.
Post reply on HN