ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial2 min readDisconfirmAI Editorial

ScaleOps Founder Yodar Shafrir: The Idle-Spike Pattern of AI Agents Renders Static Resource Planning Obsolete

In an interview at KubeCon, ScaleOps founder Yodar Shafrir explained that AI agents wait for human or other agent inputs and then execute tasks in bursts after calling large language models. Teams must provision resources for peak loads while agents hold memory throughout the waiting period, causing agents to crash due to resource shortages 80% more frequently than traditional microservices. Consequently, static scaling mechanisms are no longer applicable in the era of agents.

2026-11-18 04:35 GMT+8

Yodar Shafrir, founder and chief executive officer of ScaleOps Inc., offered a specific assessment regarding AI agent infrastructure during an interview with theCUBE Research at KubeCon + CloudNativeCon NA (United States). He argued that the behavioral patterns of agent workloads differ fundamentally from those of traditional microservices, creating dual risks of waste and failure for static resource configurations.

Shafrir described this agent behavior pattern as follows: an agent waits for input from a human or another agent, calls upon a large language model, and then executes its task in a burst. Teams must provision resources for the highest peak, while the agent continuously holds memory during the entire waiting period. When resources are insufficient, crashed steps must be rerun, consuming tokens again. He stated that ScaleOps has observed agents crashing due to resource shortages 80% more frequently than traditional microservices.

This mechanism explains why traditional auto-scaling strategies fail in agent scenarios. The idle-to-spike switching of agents occurs without warning, meaning static resource configurations either result in waste or face the risk of failure. Shafrir believes that humans and all traditional scaling capabilities are largely irrelevant at this current stage because they are too static and require manual configuration; when changes are this dynamic, they no longer function in the same way.

Sign in / Sign up
ReadingResearchRadarInvestment framework

ScaleOps's response is real-time resource decision-making: adjusting allocations, replica counts, and node placement for every application, agent, and Model Context Protocol server. The company claims this can reduce cloud costs by 70% to 80%. Additionally, ScaleOps allows other workloads to utilize resources while agents are idle and employs memory swapping so that agents receive memory only when needed. The company states this improves the cost efficiency of running agents by 90% without requiring a move away from Kubernetes.

Customers such as Adobe Inc. and Salesforce Inc. initially ran the platform in read-only mode to build trust. Shafrir stated that ScaleOps learns the historical patterns of each application, understanding their connections, communication partners, and business states.

It should be noted that this interview was sponsored by ScaleOps, and all performance figures are self-reported by the vendor, lacking independent benchmark verification. Shafrir's statement regarding the 80% higher agent crash rate stems from ScaleOps' own observations; the specific measurement methods and sample scope were not disclosed in the interview.

Sources

  • siliconangle.comSiliconANGLE↗
Continue researching →