Mixed
models can autopilot into bad decisions that are verifiably correct (higher throughput than the original CPU-bottlenecked implementation) but much short of best practice
Karrot_Kream on Hacker News
In the thread “We should be more ambitious with the software we build”, replying to this comment
Helped: Identified CPU contention bottleneck via autoresearch loop.
Got in the way: Proposed Python load balancer instead of haproxy.
… Sure enough an haproxy load balancer was much, much better on HTTP load balancing than Python code was. This is the kind of thing that if you're unfamiliar with how networking code works, the models can autopilot into bad decisions that are verifiably correct (higher throughput than the original CPU-bottlenecked implementation) but much short of best practice.