Microsoft Is Finally Racing the CPU to Sleep, and Somehow That's Controversial

Microsoft is testing a feature in Windows 11 that briefly maxes out the CPU clock whenever you open the Start menu, launch an app, or right-click for a context menu. Internally they're calling it the "Low Latency Profile," and early benchmarks from Windows Central show it cuts Start menu and context menu launch times by up to 70%, with in-box apps like Edge and Outlook opening about 40% faster. The mechanism is almost boringly simple: when a high-priority UI action triggers, the CPU spikes to maximum frequency for 1 to 3 seconds, finishes the work fast, and drops back to idle. This is the "race to sleep" pattern — burn a little more power right now to get back to a low-power state sooner — and it's been standard practice in processor design for years. The twist isn't the feature. It's that people got mad about it.

When news of the Low Latency Profile started circulating, a segment of Windows users accused Microsoft of "cheating" — leaning on raw CPU grunt instead of fixing its allegedly bloated code. Microsoft and GitHub VP Scott Hanselman responded with what I can only describe as the energy of someone who has been answering the same question since the Bush administration. "All modern operating systems do this, including macOS and Linux," he wrote. "It's not 'cheating'; this is how modern systems make apps feel fast: they temporarily boost the CPU speed and prioritize interactive tasks to reduce latency." He also added, with the weariness of a veteran forum-dweller, that "everything is a conspiracy when you don't know how anything works." Hanselman's not wrong — race-to-sleep is the reason your phone feels snappy when scrolling and then cool when idle, and Linux's cpufreq governors have been doing scheduler-driven frequency boosts for ages. But his defense dances around a more uncomfortable question, which Ars Technica's Andrew Cunningham was quick to flag: if this technique is so universal, why wasn't Windows already doing it for core UI elements like the Start menu?

The answer probably sits somewhere between legacy architecture and shifting priorities. Windows 11 inherited UI components that trace back through multiple generations of the NT kernel, and Microsoft spent the last few years pouring engineering resources into AI features — Copilot integrations, Recall, the whole generative push — while basic UI responsiveness became a recurring complaint thread on every Windows subreddit. The Low Latency Profile is part of the company's "Windows K2" quality push, which also includes refactoring legacy code paths and migrating components to WinUI 3. A burst of CPU clock speed isn't a substitute for well-architected software, but it's also not nothing. If the same hardware feels noticeably faster after an update, most people aren't going to care whether the improvement came from cleaner code or smarter scheduling. What's worth watching is whether this becomes a crutch — a reason to defer deeper fixes because the CPU can paper over the lag. The race to sleep works, but only if you're actually racing toward something better.

Sources

  • Ars Technica — "Microsoft will lean on your CPU to speed up Windows 11's apps and animations" (Andrew Cunningham, May 12, 2026) — link
  • Windows Central — "We uncovered a major Windows 11 performance upgrade Microsoft is testing" (Zac Bowden, May 7, 2026) — link

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

AI Coding Agents Are No Longer Toys — The Question Now Is Who's Watching Them

Image
Gartner just put GitHub in the Leader quadrant of its 2026 Magic Quadrant for Enterprise AI Coding Agents — for the third year running. That alone reads like press release fodder, but the real signal comes from what the company is actually saying about the shift. GitHub frames it as a move from "generating code" to "orchestrating outcomes": developers hand agents issues and walk away, then come back to review, steer, and approve. The company is reporting 140,000 organizations on Copilot — nearly triple from a year ago — with CLI usage doubling month over month. Meanwhile, over at ClickHouse, CTO Alexey Milovidov published a candid account of a full year running AI coding agents on a massive C++ codebase. His framing is useful because it doesn't hide the learning curve. Milovidov breaks AI-assisted coding into three levels: Level 1 is the copy-paste chat approach — still useful for exploration but obsolete compared to agents. Level 2 is agents running in your C...
Read more