When Compute Is Bottlenecked, Why 'Pause New, Protect Old' Is the Right Move for PMs

When your product suddenly gets more users than expected and computing power becomes the bottleneck, what would you choose? Do you let new users in to queue together, or close the new entry points to prioritize the experience of existing users? Kimi gave an "automotive-grade" answer: pause C-end new user subscriptions and bet all limited computing power on already subscribed users.