Loading video...
Video Failed to Load
It's here: We just hit superhuman performance on AI kernel optimization! Real customer models & production settings. Not toy problems (what I typically see). This is the year that Claude writes its own kernels, Codex its own kernels, for every new GPU that it wants to run on --... show more
247,624 views • 7 months ago •via X (Twitter)
35 Comments

Focus on composability of inference optimizations for ROCm stack in order to defeat the CUDA moat. (wide EP + disagg + FP4 + KV offloading + more) for maximum efficiency/scaling on huge models. AMD/ROCm lags in making those combinations smooth

Kernel wins are real only if they hold across model families. What are the p95 speedup and numerical-drift deltas on held-out production workloads?

I agree that's ideal and we do see generated kernels that generalize, but also the "real only if" part is not necessarily true in the frontier world

There goes Nvidia's moat!

Awesome, now jointly auto optimize sharding and communication strategy. Hand AIAI an AMD cluster and a training script and give them 5 million dollars to retrain Olmo3 and prove you've solved the hard problems, and it's bye bye Nvidia moat 👋

AI writing optimized kernels is basically AI becoming part of the compiler stack. Model → code → benchmark → iterate. Not more compute — just better use of the compute we already have. 🐒 🤖

Can you share a preprint or GitHub repo? Am also working on a fork of cuda agent from bytedance on an optimized kernel writing agent. Would love to benchmark

here's the tool/mcp that helped (3000x more token efficient at regular profiling/benchmarking) working on open-sourcing the end to end pipeline you see in the gif

superhuman kernel optimization on production workloads is a massive unlock. the gap between "works on benchmarks" and "works in prod" is where most projects die. this actually matters.

Finally! No more months porting CUDA code. I'm wondering if Germany can even power these optimizations, let alone deploy them.

shit is about to hit the fan

He does it in p*thon, so it's not impressive

Heard of triton and gluon?

This is a watershed moment. AI writing its own kernels means the optimization loop closes - systems improving themselves at the hardware level. Can't wait to see what comes next.

ai writing its own gpu kernels means the cuda moat is on borrowed time. software eats hardware advantages eventually

Awesome!

Nice and cool!

Portability across driver stacks still shows edge cases, real workloads test the limits

moving away from Nvidia would be a dream come true. Excited to be able to test this out one day.

Just read this three times. The implications are wilder than most people realize. @Modular @latent_ai — you're both deep in this world. Curious what you're seeing on the hardware side.

wow

honestly I'm surprised how long it took to get to this point which is why I'm saying you guys need to replan hardware immediately with this in mind, it's not just about no moat it's about because the cost of a gpu port just dropped dramatically you now have a ton of potential non-AI problems to consider, they need hardware mods which likely can dovetail with AI speedups, tensor core utilization for non-AI problems is 0 and everything gets limited by global memory bandwidth and the low end of useful device utilization I'm early on this, not wrong - it's absolute common sense.

This hits different. Superhuman optimization on real customer workloads, not toy problems, means we're talking about genuine compute multiplication. The screenshot showing active kernel compilation just makes it real.

“Real customer models” and “production settings” is the key distinction. Toy kernel benchmarks hide scheduler and memory-path pathologies that show up the second you leave the lab.

Codex is bad at following instructions, really goes on its own , despite being told not to.

nice :) can you make kernel sing - your own personal jesus? @realSharonZhou @linuxfoundation

Who still waits until June? 🤖💥 Get your workflows streamlined with The Document Chaser!

The GPU vendors saw this coming 18 months ago. That's why the compiler teams got quietly doubled. Now the race is who ships the runtime first, not who writes better CUDA.

In 2026, Claude and Codex write their own kernels. What used to take months to port between GPU generations now happens in real-time. If you aren't architecting for Self-Optimizing Compute, you're just providing exit liquidity for the next frontier model.

Hi everyone. I've been working on a measurement-based method of achieving true time dilation. 3 years it took me to perfect the mechanism. Doesn't require extreme mass or light-speed travel. It requires two independent clocks. And: you can use code to achieve it. If you have access to Codex/Cursor, copy and paste the prompt from my article. Take 10 minutes to read and understand the mechanism first, what the prompt requires so you know I'm not bluffing, then test it out for yourselves

Ahh, nvidia says on their gpu tuning guides you will probably get better results using any old stock optimiser Bayesian or genetic etc to select kernel settings for your particular load.. Optuna does this way faster than burning AI tokens.. but you do you.

Sharon you are my idol, unbelievable

this is super interesting. feels like the real bottleneck shifts from profiling to verification pretty fast. getting a faster kernel is one thing. knowing it didn’t game the benchmark or introduce subtle drift is the harder part.

Fk AI

The real unlock is eliminating the GPU porting bottleneck — if AI auto-generates optimized kernels per architecture, new hardware becomes instant capability instead of months of migration pain. That recursive loop between model intelligence and compute efficiency is where scaling gets exponential.
