J_ent

I occasionally tinker with stuff. Unreasonably obsessed with CRTs. Wildly interested in too many subjects. He/Him.

[J_ent @JohnBscv]

@timmac Hey, Tim! I'm sorry to hear you're going through a tough time! Always here to chat if you want to catch up! Hope it eases up for you soon!

[J_ent @JohnBscv]

@Pokket At least it didn't happen at random! Oh... wait

[J_ent @JohnBscv]

@Puddles_CB @Twitch IVS is a team at Twitch, which also happens to behind the service offered by AWS.
I engineer these solutions for a living, with the entities involved.

But go off, your coping is fantastic 👌

[J_ent @JohnBscv]

@Puddles_CB @Twitch Which means that the cost per stream isn't purely the data cost out of AWS. Peering through an IX, for example, is dirt cheap. You most often pay for the port cost, cross connection, and rack space. There is no real traffic cost.

[J_ent @JohnBscv]

@Puddles_CB @Twitch So it seems to mostly be a mix between whatever services they use from AWS and their own bare metal infrastructure

[J_ent @JohnBscv]

@Puddles_CB @Twitch You can sit entirely inside of AWS, and still peer externally, this is no indicator or insight

[J_ent @JohnBscv]

@Puddles_CB @Twitch My clients peer directly with Twitch, this doesn't tell you anything of how their infra is setup past that point, sadly.

[J_ent @JohnBscv]

@Puddles_CB @Twitch The majority of your traffic would hit your primary CDN that's based on content servers that peer directly with a provider's network, most likely at an IX. When you are unable to serve from a nearby content server, you fallback to an expensive CDN (Akamai, running on AWS, et al)

[J_ent @JohnBscv]

@Puddles_CB @Twitch Instead of having your entire infrastructure based on expensive AWS instances, you'd split up your main CDN and your fallback CDN into at least two, just like for example Netflix has done with their OCA

[J_ent @JohnBscv]

@Puddles_CB @Twitch My clients peer directly with Twitch, which unfortunately gives us no public insight into what exactly is past that point. It could still be AWS and still hit similar traffic costs, but that would be an absolutely awful design in terms of OPEX

[J_ent @JohnBscv]

@Puddles_CB @Twitch If Twitch has built their entire CDN on AWS using public traffic pricing, they've sadly created an extremely unnecessarily expensive environment and it'd be amazing that they're able to keep up with the traffic costs at all.

[J_ent @JohnBscv]

@Puddles_CB @Twitch If Twitch has built their CDN on the pure basis of public AWS pricing, they've understandably got a poor pricing model in place to support it. This would be shocking if it was the case, and not really feasible.

[J_ent @JohnBscv]

@Puddles_CB @Twitch You've missed the point. AWS stated traffic costs to the customer are vastly higher than their actual cost. My stated traffic costs is what you can expect from a tier 1 transit provider. AWS cost is much lower than the numbers I've stated.

[J_ent @JohnBscv]

@Puddles_CB @KristenRaeTTV @Twitch The computational power to propagate a stream is relatively negligible. Transcoding is a different matter. It'll still not be 95% of their cost, else something is horribly inefficient.

[J_ent @JohnBscv]

@Puddles_CB @KristenRaeTTV @Twitch AWS stated cost to customers is incredibly high relative to their own cost. 1200 USD per month transit (the most expensive type of traffic) will get you at the very least around 4 Gbps flatrate, or just shy of 1.3 PB of traffic. AWS pays much less than that.

[J_ent @JohnBscv]

@xndra @rolfvenema Since it'll essentially also be a dock for your laptop, I'd recommend ensuring it has the desired ports. Some monitors also have a built-in network adapter so your laptop can be wired to the network rather than using WiFi while docked.

[J_ent @JohnBscv]

@xndra @rolfvenema I personally had comfort issues with 3440x1440 at 34 inches, especially going from the high PPI built-in display of the MacBook. My recommendation is something higher, like 5120x2160 at 34 inches. Make sure it also has USB-C that can deliver enough power, and...