Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Network Service Tiers

cloudplatform.googleblog.com

Post reply on HN
Print view View original

161–170 of 215 posts

Re: Introducing Network Service Tiers

#161

Post by Animats »

daxorid wrote: post #152
Animats wrote: post #109

Earlier quoted context omitted.

Here are Codero's terms.[1] There's a procedure for dealing with breaches of the agreement, with 7 day and 30 day notices to cure. It's not one-sided, like Google's: "Google may terminate this Agreement for its convenience at any time without liability to Customer."[2] Do you want to bet your business on that? [1] http://codero.cachefly.net/docs/legal/TOS.pdf [2] https://cloud.google.com/terms/

This is great. Thank you.

Codero, although they now offer cloud services, started as a raw rackmount PC service, which is what I use them for. That business is generally run as equipment leasing - you lease for a term, and can renew. Those businesses generally have reasonable terms of service, because they're almost entirely business to business and the other side has lawyers.

Re: Introducing Network Service Tiers

#162

Post by ValentineC »

Johnny555 wrote: post #144
yeahokwhatever wrote: post #131

Earlier quoted context omitted.

Google Glacier, aka G2. I checked it out. I like that I don't have to do calculus to understand how I'll be billed, or write my own retrieval software.

AWS has greatly simplified their Glacier pricing from the inscrutable transfer rate pricing to more common sense latency based pricing. If you want your data back in AWS Glacier is cheaper per month than Google ColdStorage, but Google doesn't charge more for faster access to your data. So maybe you still need that Calculus to figure out which is a better deal for your data access pattern.

This does not include standard AWS egress pricing, which is something like $92/TB.

Re: Introducing Network Service Tiers

#163

Post by boulos »

Animats wrote: post #62

Don't sign up for a Google service unless you get contract terms which say they can't terminate you at will and have penalties if they do.

Disclosure: I work on Google Cloud (but IANAL)

https://cloud.google.com/terms/ has explicit language around termination, disagreements around billing, breaking the law, etc. Sections 4 and 9 are probably the most relevant. Again, I'm not a lawyer, but read the indemnification and so on. Unlike other services at Google, we have real, paid, 24x7 support. I understand the general concern, but I think it's misplaced in this case.

[Edit: whoops, missed your comment downthread. I'll circulate internally with legal]

Re: Introducing Network Service Tiers

#164

Post by chetanahuja »

TheSockStealer wrote: post #65
brunoTbear wrote: post #54

I quite like the way Google has drawn the map here-since no cables reach from India to Europe, they've split the map there making the paths easier to trace between Asia and NA. https://2.bp.blogspot.com/-QvF57n-55Cs/WZypui8H8zI/AAAAAAAAE... Compare with the difficulties of https://cloud.google.com/images/locations/edgepoint.png Elegant and subtle work. Just like the networking.

Nice find. What is the ping time from India to Iran? That is a long trip for a packet.

You want to see some weirdly long ping times... try pinging Israel to Turky. Compare that to say, Israel to Netherlands.

Re: Introducing Network Service Tiers

#165

Post by c0nsumer »

rb808 wrote: post #77
_7iun wrote: post #50

A long standing complaint of mine is that Cloud egress pricing severely limits the usefulness of compute. If I want to say process some visual effects on a large (1TB) ProRes video, I might spend $1 on the compute but $100 on the egress getting it back. Unfortunately these changes don't really resolve that problem. "Standard" pricing is a paltry 20% less. That 1TB video egress still costs $80 and for that price I can…

I was going to back up my photos to AWS Glacier before noticing that retrieval costs are multiple times the storage cost. I guess that is possibly OK for a backup but scared me into a physical alternative. http://liangzan.net/aws-glacier-calculator/

As a suggestion, I use Glacier (with Arq) as a tertiary backup. If I have to go to that it means a lot of other things failed and I'll be willing to pay the price.

Re: Introducing Network Service Tiers

#166

Post by CodeWriter23 »

dimva wrote: post #122
nealmueller wrote: post #102

Earlier quoted context omitted.

I worked on this product release, at Google. Can you guide my eye please where we don't specify TB? I'll get that fixed. I took a look and it says TB. @nealmueller if that's easier for you.

You are right, it does say TB everywhere, and does not mention GB anywhere. But, if this is correct and all prices are per TB, that would be a ~1000x price cut compared to your current pricing, which is per GB.

Page has been updated to say "per GB" (in bold, lol)

Re: Introducing Network Service Tiers

#167

Post by Johnny555 »

ValentineC wrote: post #162
Johnny555 wrote: post #144

Earlier quoted context omitted.

AWS has greatly simplified their Glacier pricing from the inscrutable transfer rate pricing to more common sense latency based pricing. If you want your data back in AWS Glacier is cheaper per month than Google ColdStorage, but Google doesn't charge more for faster access to your data. So maybe you still need that Calculus to figure out which is a better deal for your data access pattern.

This does not include standard AWS egress pricing, which is something like $92/TB.

Right, and it doesn't include standard GCE egress pricing, which is something like $120/TB.

https://cloud.google.com/storage/pricing

Re: Introducing Network Service Tiers

#168

Post by Veratyr »

boulos wrote: post #159
_7iun wrote: post #154

Earlier quoted context omitted.

The problem is often I need that data locally. With video editing in particular, I can't work with data that's not local and I can't run my editing software in the cloud because I'm not aware of any kind of remote workstation that offers colour management and whatnot.

Teradici does do this. Feel free to send me an email :). Disclosure: I work on Google Cloud.

Are you aware of anything else that does this? I'm an individual so nothing with "Contact Sales" is useful to me.

Re: Introducing Network Service Tiers

#169

Post by boulos »

Veratyr wrote: post #168
boulos wrote: post #159

Earlier quoted context omitted.

Teradici does do this. Feel free to send me an email :). Disclosure: I work on Google Cloud.

Are you aware of anything else that does this? I'm an individual so nothing with "Contact Sales" is useful to me.

I didn't say to Contact Sales, I said to contact me :).

Remote desktop with super accurate color instead of lots of dithering and compression is tricky. Are you on Windows or Linux?

Re: Introducing Network Service Tiers

#170

Post by packetslave »

arthurcolle wrote: post #158
_7iun wrote: post #50

A long standing complaint of mine is that Cloud egress pricing severely limits the usefulness of compute. If I want to say process some visual effects on a large (1TB) ProRes video, I might spend $1 on the compute but $100 on the egress getting it back. Unfortunately these changes don't really resolve that problem. "Standard" pricing is a paltry 20% less. That 1TB video egress still costs $80 and for that price I can…

What is egress in this context? What is ProRes? Just curious

if only there were some way to find detailed information to satisfy your curiosity using the Internet. some kind of "searching engine", perhaps.
Post reply on HN