Oracle taps AMD CPUs and networking chips for its next cloud compute generation
The collaboration targets the CPU work around AI models and moves infrastructure tasks onto dedicated chips. E7 remains an upcoming service, not a completed rollout.
Loading page…
The collaboration targets the CPU work around AI models and moves infrastructure tasks onto dedicated chips. E7 remains an upcoming service, not a completed rollout.
Listen to this story
Oracle and AMD used Oracle AI World on October 27, 2026, to outline OCI’s next AMD-based compute generation: upcoming E7 instances built on sixth-generation EPYC “Venice” CPUs, plus Pensando-powered Acceleron network cards that offload networking, storage and security from host CPUs. The design targets enterprise application work around AI inference, including agent orchestration, retrieval and tool execution—not just model generation. E7 availability is not committed; customers should benchmark CPU/GPU balance and cost per token or completed workload rather than infer performance from processor specifications.
EPYC 9006 processors are specified at up to 256 cores, 512 threads per socket and 16 memory channels; these are chip maxima, not per-VM allocations.
E7 Acceleron Standard VMs will offer flexible CPU and memory configurations for workloads such as retrieval services, caches and concurrent agent sandboxes.
Oracle says the Acceleron cards isolate customer and cloud-managed functions, and their programmable design allows infrastructure services to change as workloads evolve.
Oracle’s next AMD-based cloud compute generation will address both application processing and the infrastructure work competing for it. At Oracle AI World on October 27, 2026, the companies detailed upcoming E7 instances using sixth-generation AMD EPYC processors, alongside Pensando chips that handle networking, storage and security tasks for AMD-powered Oracle cloud instances.
The collaboration update extends AMD’s multigeneration relationship with Oracle Cloud Infrastructure, or OCI. Its E7 component focuses on enterprise applications and the CPU services surrounding AI models, rather than just the computing used to generate a model’s answers.
Oracle’s companion announcement describes that work in concrete terms: CPUs assemble context, route actions, retrieve knowledge, query databases, parse documents and execute tools. These steps affect application performance alongside model inference—the process of running a trained model to produce a response.
E7 is intended to support several layers of that application stack, not a single agent function:
Oracle identifies E7’s processors as sixth-generation EPYC “Venice” CPUs from AMD’s EPYC 9006 series. It lists processor capabilities of up to 256 cores and 512 threads per socket, plus 16 memory channels. Those are processor specifications, not a disclosed allocation for every E7 virtual machine.
E7 Acceleron Standard virtual machines will offer flexible CPU and memory configurations. Oracle says customers can match those resources to their services, while the processors’ standards-based x86 foundation supports continuity with existing enterprise software stacks.
The networking side tackles a different demand on the host processor. Oracle Acceleron network interface cards for AMD compute and accelerator instances incorporate Pensando data processing units, or DPUs. These dedicated chips accelerate networking, storage and security functions in hardware. AMD says that preserves host CPU capacity for customer applications.
Oracle says the co-engineered cards combine host networking and cloud-control functions in one architecture while keeping customer and cloud-managed functions isolated. Their programmable design lets OCI change networking, storage, security and observability services as workloads evolve, rather than treating the hardware’s infrastructure role as fixed.
Oracle’s guidance puts workload testing ahead of a universal hardware prescription. It recommends evaluating CPU capacity, the number of tasks running at once and response-time targets alongside GPU requirements. Flexible sizing provides a way to adjust resources; testing determines the balance an application actually needs.
The company also points to cost per token—the pieces of text a model processes or produces—or completed workloads as practical measures of value. Its proposed assessment is application-specific: judge the resources against the performance a service needs, rather than treating a processor’s headline specifications as the final result.
Loading discussion...
Join the conversation
Explain which part of an AI service deserves more scrutiny.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.