zlacker

[return to "From slow to SIMD: A Go optimization story"]
1. blobbe+WK[view] [source] 2024-01-23 21:09:48
>>rbanff+(OP)
This is the type of optimization we used to see in embedded hardware constrained environments.

Nowadays, even on most embedded platforms resources are so abundant and applications are HORIZONTALLY scaled that it seems to feel like nobody bothers with VERTICAL scaling.

The thing about multiplication is it is commutative; an 8x improvement in performance of a single node means you need 8x less nodes! What a fun way to cut down your AWS bill and send your SaaS company to profitability.

◧◩
2. whatsh+BL[view] [source] 2024-01-23 21:13:21
>>blobbe+WK
I don't know the truth about it, but what people say is that most unprofitable SaaS startups are the way they are because they're making no money at all, not that their costs are higher than their 2x-one-developer's-compensation revenues.
◧◩◪
3. __loam+kQ[view] [source] 2024-01-23 21:34:55
>>whatsh+BL
I think there's plenty of sass companies out there that are subsidizing what their customers are paying them with vc cash. I've been at 2 sass companies where infrastructure optimization was starting to be a real concern. If your unit economics are in the red and additional customers cost you money, you need to optimize somehow.
[go to top]