Saturday, August 15
Saturday, August 15
A Developer Set Up an Optimization Loop With Codex. It Found a 232x GPU Speedup.

Developer Sankalp Shubham pointed OpenAI's Codex at a batched QR decomposition kernel, gave it an automated benchmark, and let it iterate without supervision. The kernel went from 419,000 µs to 1,805 µs. That's a 232x speedup on a Saturday morning's worth of compute. The conversation blowing up around this post isn't really about the number, though. It's about the setup: a clear optimization target, an automated way to check results, and an LLM grinding through the solution space like it has nowhere else to be. People are already mapping this pattern onto compiler tuning, materials science, drug binding — anywhere "did it improve?" has a computable answer.
Favorite Featured Stories

Three engineers argued in 1984 that only the two ends of a conversation can judge whether an exchange came out right. TC...

Most agents in production stop somewhere around ten steps and hand the work to a person. Easy to read that as the models...

The machine-readable layer of your website used to be decoration. A few structured tags under the product page, worth a ...

Watch a coding agent work for an hour. Forty files, tests written and failed and rewritten, and when it stops, no user h...