On: WebSockets cost us $1M on our AWS bill

[londons_explore]

They are presumably using the GPU for video encoding....

And the GPU for rendering...

So they should instead just be hooking into Chromium's GPU process and grabbing the pre-composited tiles from the LayerTreeHostImpl[1] and dealing with those.

[1]: https://source.chromium.org/chromium/chromium/src/+/main:cc/...

[orf → londons_explore]

One of the first parts of the post explains how they are using CPUs only

[mbb70 → londons_explore]

They are very explicit in the article that they run everything on CPUs.

[isoprophlex → londons_explore]

You'd think so but nope, they deliberately run on CPU, as per the article...

[yjftsjthsd-h → isoprophlex]

> We do our video processing on the CPU instead of on GPU, as GPU availability on the cloud providers has been patchy in the last few years.

I dunno, when we're playing with millions of dollars in costs I hope they're at least regularly evaluating whether they could at least run some of the workload on GPUs for better perf/$.

[londons_explore → yjftsjthsd-h]

And their workload is rendering and video encoding. Using GPU's should have been where they started, even if it limits their choice of cloud providers a little.