Most teams building agents on AWS assume GPU is where the compute goes. It's usually not.Â
In this session, Dr. Ryan Ries and Marty Neuhard traced a real agentic AI request on AWS from start to finish and showed where the compute actually lands.Â
Marty and Ryan were joined by Ray Prado at AMD about scaling agentic AI with AMD EPYC. These processors are crucial for the advancement and implementation of Agentic AI. EPYC’s performance and core count flexibility within the AWS instance portfolio enables whatever shape your agentic workload requires. Â
Key Takeaways:Â
Where your AI agents spend their computeÂ
The real breakdown of CPU vs. GPU work across an agentic AI system, and why it's not what most teams assume.Â
How to size compute correctly for agentic AI on AWSÂ
A practical way to evaluate what each step of your workflow actually needs, instead of defaulting to GPU across the board.Â
What this means for your AWS costsÂ
Where teams typically overprovision, and what to check before your next GPU spend decision.Â