WebSockets cost us $1M on our AWS bill

Did they originally NOT run things on the same machine? Otherwise the WebSocket would be local and incur no cost.

Did you read the article? It is about the CPU cost of using WebSockets to transfer data over loopback.

our websocket traffic is roughly 40% of recall.ai and our bill was $150 USD this month using a high memory VPS

>WebSocket would be local and incur no cost.

The memcopys are the cost that they were paying, even if it was local.

I read the entire article and that wasn't my takeaway. After reading, I assumed that AWS was (somehow) billing for loopback bandwidth, it wasn't apparent (to me) from the article that CPU costs were the sticking point

> We set a goal for ourselves to cut this CPU requirement in half, and thereby cut our cloud compute bill in half.

From the article intro before they dive into what exactly is using the CPU.

The article describes why this isn't the problem. You might enjoy reading it.

The basic point is that WebSockets requires that data move across channels that are too general and cause multiple unaligned memory copies. The CPU cost to do the copies was what cost the megabuck, not network transfer costs.