{"id":141521,"date":"2026-08-16T15:13:12","date_gmt":"2026-08-16T15:13:12","guid":{"rendered":"https:\/\/www.europesays.com\/ai\/141521\/"},"modified":"2026-08-16T15:13:12","modified_gmt":"2026-08-16T15:13:12","slug":"agentic-ai-crunch-creates-cpu-comeback","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ai\/141521\/","title":{"rendered":"Agentic AI Crunch Creates CPU Comeback"},"content":{"rendered":"<p>Earlier this year, leaders at <a href=\"https:\/\/aws.amazon.com\/free\/?trk=dc9b9d60-cc82-4cd5-8a61-0b33d6a79fab&amp;sc_channel=ps&amp;ef_id=CjwKCAjw1vXTBhB-EiwAEKr_k_57Xoz6QKQSrRqDF4mGRYOudA_A99MTHZL6alVjPDxdliBQfEMPihoC0RUQAvD_BwE&amp;gads_camp=23532472510&amp;gads_ag=199502799824&amp;gads_ad=795877020713&amp;gads_kw=amazon%20web%20services&amp;gads_matchtype=e&amp;gads_network=g&amp;gads_device=c&amp;gads_geo=9198314&amp;gad_campaignid=23532472510&amp;gbraid=0AAAAADjHtp-SgwVQvE7H9V8lK49jVtMDw&amp;gclid=CjwKCAjw1vXTBhB-EiwAEKr_k_57Xoz6QKQSrRqDF4mGRYOudA_A99MTHZL6alVjPDxdliBQfEMPihoC0RUQAvD_BwE\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">Amazon Web Services<\/a> delivered a new mandate to their engineers: they need to conserve CPU cycles at all costs. AWS has <a href=\"https:\/\/www.theinformation.com\/articles\/aws-tells-engineers-cut-cpu-waste-amid-crunch\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">reportedly<\/a> experienced an explosion in wait times for CPU server capacity as AI workloads strain the company\u2019s cloud infrastructure. <\/p>\n<p>The issue seemingly took AWS off-guard, and for good reason. The AI boom led to a surge in demand for <a href=\"https:\/\/spectrum.ieee.org\/nvidia-gpu\" target=\"_self\" rel=\"nofollow noopener\">GPUs<\/a> and, later, <a href=\"https:\/\/spectrum.ieee.org\/high-bandwidth-memory-shortage\" target=\"_self\" rel=\"nofollow noopener\">memory<\/a>. CPUs were mostly left out of the story, as their relative lack of parallelization made them a poor fit for AI model inference, the process of running and serving <a href=\"https:\/\/spectrum.ieee.org\/tag\/large-language-models\" rel=\"nofollow noopener\" target=\"_blank\">large language models<\/a> (LLM) to users. <\/p>\n<p>But the rise of agentic AI systems, which allow <a href=\"https:\/\/spectrum.ieee.org\/tag\/ai-models\" rel=\"nofollow noopener\" target=\"_blank\">AI models<\/a> to operate autonomously and call on sub-agents, is changing the narrative.<\/p>\n<p><a href=\"https:\/\/moorinsightsstrategy.com\/team\/matt-kimball\/\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">Matt Kimball<\/a>, vice president and principal datacenter analyst at <a href=\"https:\/\/moorinsightsstrategy.com\/\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">Moor Insights &amp; Strategy<\/a>, says 2026 has brought a spike in CPU demand, much of it due to <a href=\"https:\/\/spectrum.ieee.org\/ai-agents\" target=\"_self\" rel=\"nofollow noopener\">agentic AI<\/a>. \u201cIt\u2019s one thing to have this agentic workload, and let\u2019s say, it spawns 100 agents. If I\u2019m going to roll this out across my enterprise, those 100 become tens of thousands, hundreds of thousands, or millions of agents,\u201d says Kimball. \u201cYou have agents spawning sub-agents, making [application programming interface (API)] calls, and talking to more agents through [Anthropic\u2019s] model context protocol.\u201d<\/p>\n<p>AI agents need to use computers, and computers need CPUs<\/p>\n<p>Kimball\u2019s comments refer in part to \u201ctool use,\u201d which is shorthand for an LLM\u2019s ability to access the internet, open files on a desktop, and generally use a variety of software to accomplish its task. <\/p>\n<p>LLMs trained for tool use learn how to call on other software. While the LLM\u2019s inference is still primarily executed on a GPU or similar AI accelerator, the tool calls the LLM makes are typically pushed to the CPU.<\/p>\n<p>\u201cMany components of an agentic AI task are inherently CPU based jobs,\u201d explains <a href=\"https:\/\/www.linkedin.com\/in\/souvik-kundu-64922b50\/\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">Souvik Kundu<\/a>, senior staff research scientist at <a href=\"https:\/\/www.intel.com\/content\/www\/us\/en\/homepage.html\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">Intel<\/a>. \u201cThe CPU does the job of parsing output, figuring out which tool to invoke, making the API call or running the code, collecting the result, and feeding it back.\u201d <a href=\"https:\/\/www.linkedin.com\/in\/mrangarajan\/\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">Madhu Rangarajan<\/a>, vice president of compute and enterprise AI at <a href=\"https:\/\/www.amd.com\/en.html\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">AMD<\/a>, makes a similar claim, saying \u201cin our testing, seven of the eight stages in realistic agentic AI pipelines run entirely on the CPU.\u201d<\/p>\n<p>An LLM tasked with programming software, for example, will likely make tool calls to write code to files, move or replace files, download required packages, and build the software once the LLM believes it\u2019s complete. <\/p>\n<p>Kundu co-authored a <a href=\"https:\/\/arxiv.org\/pdf\/2511.00739\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">paper<\/a> on agentic AI optimization alongside researchers from the Georgia Institute of Technology. They found the CPU is often idle while LLM inference is executed on a GPU and that, conversely, the GPU is often idle when tool calls are executed on the CPU. To optimize this, Kundu and his colleagues propose scheduling optimizations that can cut end-to-end latency (the time between the start and finish of the agentic workload) by up to 1.8x under sustained load. <\/p>\n<p>It\u2019s a start, but the gains chase a moving target. Agentic systems generate work at machine speed and multiply it as they go. OpenAI\u2019s inadvertent <a href=\"https:\/\/spectrum.ieee.org\/hugging-face-openai-cyberattack?itm_source=homepage&amp;itm_medium=hero&amp;itm_campaign=hero-2026-08-10&amp;itm_content=hero6\" target=\"_self\" rel=\"nofollow noopener\">hack<\/a> of Hugging Face saw its model fire off as many as 300 actions an hour, and a single agent can spawn sub-agents that make tool calls of their own. <\/p>\n<p>And there\u2019s one more important complication that may increase the workload on a CPU as models become more complex: safety guardrails.<\/p>\n<p>Safety and policy checks on an agent\u2019s actions are often specific rules that inspect syntax and log files, Kundu says. Guardrails may also use small models (under a billion parameters) to analyze task complexity or intent. Though they could be executed on a GPU, they often aren\u2019t, because their small size and the need to minimize latency keeps the work on the CPU.<\/p>\n<p class=\"shortcode-media shortcode-media-rebelmouse-image\"> <img loading=\"lazy\" decoding=\"async\" alt=\"A bar graph illustrating how the latency for Llama-8B\\u2019s LLM becomes 4.45 times less when the number of CPU cores is increased from five to thirty-two.\" class=\"rm-shortcode rm-lazyloadable-image\" data-rm-shortcode-id=\"b43d668525bb89a3e691433307b18677\" data-rm-shortcode-name=\"rebelmouse-image\" data-runner-src=\"https:\/\/spectrum.ieee.org\/media-library\/a-bar-graph-illustrating-how-the-latency-for-llama-8b-u2019s-llm-becomes-4-45-times-less-when-the-number-of-cpu-cores-is-increas.jpg?id=67615386&amp;width=980\" height=\"1499\" id=\"7acb8\" lazy-loadable=\"true\" src=\"data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20viewBox='0%200%202000%201499'%3E%3C\/svg%3E\" width=\"2000\"\/> Increasing the number of CPUs available significantly decreases the latency for Llama-8B responses over longer sequence lengths.Source: <a href=\"https:\/\/arxiv.org\/pdf\/2603.22774\" target=\"_blank\" rel=\"nofollow noopener\">Euijun Chung, Yuxiao Jia, et al.<\/a><\/p>\n<p>Tokenization adds to bottlenecks<\/p>\n<p><a href=\"https:\/\/ejchung0406.github.io\/\" target=\"_blank\" rel=\"nofollow noopener\">Euijun Chung<\/a>, a PhD student at the Georgia Institute of Technology, recently co-authored another <a href=\"https:\/\/arxiv.org\/abs\/2603.22774\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">paper<\/a>, with findings that complement Kundu\u2019s work. Chung and his co-authors found that when a server has too few CPU cores, it falls behind on dispatching work to the <a href=\"https:\/\/spectrum.ieee.org\/tag\/gpus\" rel=\"nofollow noopener\" target=\"_blank\">GPUs<\/a>. That causes the GPUs to stall as they wait for instructions.<\/p>\n<p>In addition to that, the paper touches on another key element of LLM workloads: <a href=\"https:\/\/seantrott.substack.com\/p\/tokenization-in-large-language-models\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">tokenization<\/a>.<\/p>\n<p>Tokenization is a key first step in LLM inference. It converts text into integer token IDs that can be processed by the model. Unlike the matrix math required for most LLM inference, tokenization is branchy, data-dependent sequential string manipulation. Though it can be parallelized by chunking text, it\u2019s not massively parallel in the same way as the bulk of LLM inference is.<\/p>\n<p>Tokenization of small prompts is a relatively trivial task and won\u2019t tax even an entry-level CPU. However, an agentic model that makes tool calls must parse and tokenize the results of the call. <\/p>\n<p>\u201cIf you have an ongoing sequence of, say, 100,000 tokens, and you have a tool result of a 1,000 tokens, the tokenizer will have to tokenize the whole sequence again. And you have to do tokenization at every agentic tool call,\u201d says Chung. This both increases the frequency of tokenization and increases the number of tokens involved. It\u2019s conceivable that future tokenizers will find ways to mitigate this, Chung says, but it remains a problem for modern LLM inference.<\/p>\n<p>The paper finds that time-to-first-token latency (the time required for the model to produce the first word of its reply) can increase dramatically as the sequence length grows. CPUs with more cores can reduce the problem. In test runs at longer sequence lengths, increasing CPU core counts can reduce time-to-first-token latency by roughly 1.5x to 7x. <\/p>\n<p>Chung and his colleagues were only able to test smaller models, such as Alibaba\u2019s Qwen 3-30B and Meta\u2019s Llama 3.1-70B, due to limitations of the hardware available for testing. He speculates that larger models will experience less dramatic bottlenecks due to their higher overall GPU demand, but also expects agentic AI will push token lengths far beyond the longest he and his co-authors tested.<\/p>\n<p>\u201cIf you think about something like Anthropic\u2019s Claude, you can easily hit 500,000, even a million tokens,\u201d says Chung. \u201cIn the world of agentic AI, the average sequence length will grow and grow, so I\u2019m expecting this problem to get worse in future workloads.\u201d <\/p>\n<p>Is a CPU crunch just getting started?<\/p>\n<p>Amazon\u2019s crackdown on use of CPU resources is one of several indicators that Kundu and Chung have identified issues with real-world relevance. <\/p>\n<p><a href=\"https:\/\/spectrum.ieee.org\/tag\/intel\" rel=\"nofollow noopener\" target=\"_blank\">Intel<\/a> has <a href=\"https:\/\/finance.yahoo.com\/news\/intel-turnaround-no-one-saw-141000146.html?guccounter=1&amp;guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&amp;guce_referrer_sig=AQAAAJqbhttNhPiUgZBGw-QWbgpaSpMnF0qwXSRBrSMQvCVWxhrkdpDYWyavDbXWb-9coPNWysaUbJK_l5uY_bZH6ACvfNpR8JrxKbKXsw8dVSlzZLYe9ydhDqS0SAyZbc4KSK0bqLw8WJSIYt-yoFGlGWDRP1UIaWov2q1bpzbcLPE-\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">sold out<\/a> of server CPUs through at least the end of the year. <a href=\"https:\/\/spectrum.ieee.org\/tag\/amd\" rel=\"nofollow noopener\" target=\"_blank\">AMD<\/a> has <a href=\"https:\/\/wccftech.com\/amd-doubles-server-cpu-forecast-to-120-billion-as-agentic-ai-rewrites-demand-ceo-says-epyc-verano-built-purely-for-ai\/\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">doubled<\/a> its server CPU forecast. <a href=\"https:\/\/www.arm.com\/products\/cloud-datacenter\/arm-agi-cpu\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">Arm<\/a> and <a href=\"https:\/\/www.cnbc.com\/2026\/06\/24\/qualcomm-data-center-cpu-meta.html\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">Qualcomm<\/a> have both announced new CPUs designed to accelerate agentic AI. Even <a href=\"https:\/\/www.nvidia.com\/en-us\/\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">Nvidia<\/a> has prioritized <a href=\"https:\/\/nvidianews.nvidia.com\/news\/nvidia-unveils-vera-the-cpu-for-agents\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">Vera<\/a>, its Arm-based CPU for agentic AI, which is part of Nvidia\u2019s <a href=\"https:\/\/spectrum.ieee.org\/nvidia-rubin-networking\" target=\"_self\" rel=\"nofollow noopener\">Vera Rubin<\/a> platform.<\/p>\n<p>Kimball says these developments make it clear that the AI industry is placing more emphasis on CPU performance. He sees the surge in demand as an \u201cabsolute tell\u201d that CPUs are now considered a key part of an agentic AI system.<\/p>\n<p>Unfortunately, this may translate to broader CPU shortages and increased prices, much as has already occurred with GPUs and memory. <\/p>\n<p>\u201cYou\u2019re already seeing a CPU crunch to some degree. When you look at the constraints in the market, it even trickles down into the consumer space,\u201d says Kimball. He adds that Intel has <a href=\"https:\/\/www.techpowerup.com\/345535\/intel-reallocates-pc-production-capacity-to-server-cpus-amid-tight-wafer-supply\" rel=\"noopener noreferrer nofollow\" target=\"_blank\">cut production<\/a> of client CPUs in favor of server CPUs even as Intel\u2019s new 18A production process has grown the company\u2019s sales in the client segment. Kimball sees that as a sign that CPU makers will follow the money. <\/p>\n<p>From Your Site Articles<\/p>\n<p>Related Articles Around the Web<\/p>\n","protected":false},"excerpt":{"rendered":"Earlier this year, leaders at Amazon Web Services delivered a new mandate to their engineers: they need to&hellip;\n","protected":false},"author":2,"featured_media":141522,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[179,7493,4104,2010,2225],"class_list":["post-141521","post","type-post","status-publish","format-standard","has-post-thumbnail","category-agentic-ai","tag-agentic-ai","tag-agentic-artificial-intelligence","tag-cpu","tag-gpu","tag-llms"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/141521","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=141521"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/141521\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/141522"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=141521"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=141521"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=141521"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}