Description du poste
Recently I've been hearing a lot about compute reallocation, and tbh, it seems like a bad way to go about slowing down AI progress.
To be clear: I think that we need to slow or stop AI development and I'm all for any practical solution that gets us closer to that. What I'm against is compute reallocation: the idea that we should limit what percent of a company's available compute they can spend on R&D. Specifically, Pacing AI calls to limit labs to spending at most 15% of their available compute on "capabilities R&D".
Proposed in:
• Pacing AI via Compute Reallocation by Thomas Larsen & romeo of AI 2027 fame• How California can “pace the frontier” by Secure AI Project of SB 53 fame
Instead of Compute Reallocation, I think it's preferable to have a Compute Cap, where we limit the net amount of compute available to R&D research.
Why?
• The thing we actually care about is how powerful models are. Regulating that is very difficult so instead we want to target AI inputs. Of those compute is the easiest to target. We can ~calculate how much an increase in compute corresponds to an increase in capabilities and right now I'm getting the impression that people backing this policy are using those numbers to calculate . Why not cut out the middle man and directly set the limit we want in the first place that we think would be safer?• If there is a sudden breakthrough in data center construction (ex: learning how to train on lower end GPUs), that won't translate into unforeseen capability gains.• Doing net amount decreases the incentive to build new data centers, meaning it creates (hopefully) less of a compute overhang. I suspect the demand is so large regardless that the limit remains construction speed, but in theory this is still a demand decreasing move.• One of the common concerns about AI regulation is that the big 5 will use it to make it impossible new labs to join the game. By setting a limit you make it easier for new people to join since they will only have to g