Live data from Hacker News

Introducing Network Service Tiers

cloudplatform.googleblog.com

171–180 of 215 posts

Re: Introducing Network Service Tiers

#171
post #93

Earlier quoted context omitted.

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

I was going to ask the same thing, what's up with that. Why is there no continuous connextion?

Back when I was in Google Netops we had a healthy (unofficial) fear of having the backbone connect all the way around the world in a circle, especially with high-enough bandwidth links that both directions would start to look attractive to traffic management.

Re: Introducing Network Service Tiers

#172
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 about BackBlaze's B2? It's priced much lower.

Re: Introducing Network Service Tiers

#173
post #49

Earlier quoted context omitted.

Are they exclusive owner/builders of any of those? I know I've seen a number of cables which Google was a part investor/owner in, but sole ownership would be amazing.

A "cable" is actually comprised of many dedicated fibers, that could each one transfer some Tb/s and be leased for millions. I doubt that anyone would keep ALL of them for themselves.

and each dedicated fiber can run multiple "colors" of light, so multiple customers can have their own segment of the traffic fully isolated from each other.

Re: Introducing Network Service Tiers

#175

Earlier quoted context omitted.

I wonder what that same 1 TB of data costs on the "open market" (or how it is even priced). Say I'm a smallish ISP on the east coast and want to send 1 TB to another smallish ISP on the west coast. I probably have a contract with, I don't know, AT&T or whoever owns the cables (I'm from Europe so I have no clue, in Germany it would be Telekom). I'm guessing it would probably cost cents (and that would bring my data ac…

You don't buy bytes, you buy pipes. Typically, you buy say 1Gbit of transit and you can put as much or as little data through that pipe as you want. You can get a gigabit pipe from Hurricane Electric or FDCServers for $400/month. In a month it can take 327TB of data, so the cost of 1TB is ~$1.20.

Curious - at what POP have you been quoted $400/month for a gigabit connection from HE?

Re: Introducing Network Service Tiers

#176
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

Wikipedia: "Apple ProRes is a lossy video compression format developed by Apple Inc. for use in post-production that supports up to 8K."

Egress and ingress are outgoing and incoming data, respectively.

Re: Introducing Network Service Tiers

#177

Earlier quoted context omitted.

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

Given TFA, it's probably more accurate to say $85/TB: https://cloud.google.com/network-tiers/pricing

Re: Introducing Network Service Tiers

#178
post #169

Earlier quoted context omitted.

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?

Ah, I see.

The software I need (mostly Davinci Resolve) runs on all major platforms, including Linux, so I can be on whatever I need to be.

Re: Introducing Network Service Tiers

#179

Earlier quoted context omitted.

You don't buy bytes, you buy pipes. Typically, you buy say 1Gbit of transit and you can put as much or as little data through that pipe as you want. You can get a gigabit pipe from Hurricane Electric or FDCServers for $400/month. In a month it can take 327TB of data, so the cost of 1TB is ~$1.20.

Curious - at what POP have you been quoted $400/month for a gigabit connection from HE?

Its not a quote, but a well known, long running cabinet special for 42u (aka a dedicated full rack) and 15 amps of power: https://he.net/special.pdf

Other datacenters can go cheaper if you need less rackspace and power, bandwidth is cheap!

Re: Introducing Network Service Tiers

#180
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 think part of the reason is people look at Linode/Vultr/DO and presume that 1/2TB for $5 is the market price (and then quote HE.Net/Cogent/Hibernia offering 10G to certain colos at $2-5kpm as backing proof), or dedicated servers with 10TB for $50pm etc... Linode/Vultr/DO mainly work off an average usage of 1%-2%, although at least they dont stop you deploying more boxes as you reach the limit, you can get clever and one would presume they dont invoke some TOS clause. I imagine GCP, AWS, and Azure bandwidth cost is closer to the truth at running a network that is resilent and can scale beyond 100G, the transit or costs of fiber is probably only a tiny fraction when pushing beyond 100G per region, vs your low end VPS provider, let's not forget the epic fail of Linode DDOS handling. I do agree though in comparison it sounds expensive.
Post reply on HN