Announcing Region Expansion of P4de instances on SageMaker Notebook Instances
P4de's 640GB GPU memory and 60% faster training are now available in Tokyo—cutting costs 20% vs. P4d for large-scale ML workloads.
View original announcement →Visual Summary
What's New
Amazon Web Services has expanded the availability of Amazon EC2 P4de instances to the Asia Pacific (Tokyo) region on SageMaker notebook instances, making them generally available. P4de instances are equipped with 8 NVIDIA A100 GPUs, each featuring 80GB of HBM2e GPU memory—double the memory of the existing P4d instances—for a total of 640GB of GPU memory per instance. This expansion enables customers in the Tokyo region to leverage significantly enhanced ML training performance directly within their SageMaker notebook workflows.
How It Works
- P4de instances are backed by 8 NVIDIA A100 Tensor Core GPUs, each with 80GB of high-bandwidth HBM2e memory, delivering a total of 640GB of GPU memory per instance—twice the per-GPU memory of P4d instances.
- SageMaker notebook instances provision these EC2 P4de instances as the underlying compute, running a Jupyter Notebook server pre-configured with the SageMaker Python SDK, Boto3, deep learning frameworks (PyTorch, TensorFlow), and other ML libraries.
- Users can launch P4de-backed notebook instances through the SageMaker console, CLI, or SDK by selecting the appropriate instance type (e.g.,
ml.p4de.24xlarge) when creating or updating a notebook instance. - The increased GPU memory allows larger model parameters, bigger batch sizes, and higher-resolution datasets to reside entirely in GPU memory, reducing costly memory swapping and enabling more efficient distributed training.
- SageMaker Studio's JupyterLab and Code Editor applications can also be configured to run on P4de instances, providing a full-featured IDE experience backed by this high-performance hardware.
- Underlying networking leverages high-throughput, low-latency connectivity consistent with the P4 family, supporting distributed and multi-node training workloads at scale.
Why It's Important
- The 60% improvement in ML training performance over P4d instances directly translates to faster model iteration cycles, enabling teams to experiment more rapidly and reduce time to market for AI-powered products.
- A 20% reduction in cost-to-train compared to P4d means organizations can achieve better performance economics, lowering the total cost of ownership for large-scale training workloads.
- Availability in Asia Pacific (Tokyo) is strategically significant for customers with data residency requirements, latency-sensitive workflows, or regulatory constraints that mandate compute resources remain within Japan or the broader APAC region.
- The 640GB total GPU memory pool unlocks training of very large models—such as large language models (LLMs) and vision transformers—that previously required complex model parallelism strategies or could not fit on P4d instances at all.
- Customers working with high-resolution imaging data (medical imaging, satellite imagery, industrial inspection) benefit directly from the expanded memory, enabling larger batch sizes of high-dimensional inputs without downsampling.
How It's Different
- P4de provides 80GB HBM2e memory per GPU versus 40GB HBM2 per GPU on P4d—a 2× increase in per-GPU memory capacity that fundamentally changes what model sizes and dataset resolutions are feasible in a single training run.
- Up to 60% better ML training performance compared to P4d, driven by the combination of higher memory bandwidth (HBM2e vs. HBM2) and larger memory capacity reducing data movement overhead.
- 20% lower cost to train relative to P4d instances, meaning P4de delivers both superior performance and better price-performance—not a trade-off between the two.
- Compared to P4d, P4de instances are better suited for memory-bound workloads where the bottleneck is GPU memory capacity rather than raw compute throughput alone.
- Unlike P3/P3dn instances (the prior generation), the entire P4 family (including P4de) offers 400 Gbps instance networking and GPUDirect RDMA, enabling efficient multi-node scale-out; P4de extends this with the larger memory envelope.
When to Prefer It
- Choose P4de when training large foundation models or LLMs where model parameters and optimizer states exceed the 40GB per-GPU memory limit of P4d instances, avoiding the need for aggressive model sharding.
- Prefer P4de for computer vision workloads involving high-resolution images or video frames, where larger GPU memory allows bigger batch sizes without resolution downsampling that could degrade model accuracy.
- Use P4de when operating under strict data residency or compliance requirements that mandate compute resources remain in the Asia Pacific (Tokyo) region and you need top-tier GPU training performance.
- Select P4de for iterative research and experimentation workflows in SageMaker notebooks where faster training turnaround (up to 60% improvement) meaningfully accelerates the hypothesis-test-iterate cycle.
- Opt for P4de when total training cost is a concern and you are currently using P4d—the 20% cost-to-train reduction means migrating to P4de can lower your ML infrastructure spend while simultaneously improving throughput.
- Consider P4de for multi-modal training tasks (e.g., combining text, image, and audio) where the combined memory footprint of multiple modality encoders benefits from the larger 640GB aggregate GPU memory pool.
Availability
- Status: Generally Available (GA) as of May 27, 2026.
- Newly added region: Asia Pacific (Tokyo) — this announcement specifically expands P4de availability to this region on SageMaker notebook instances.
- Prior regions: P4de instances were already available in other AWS regions before this expansion; Tokyo represents the latest addition.
- Supported surfaces: Available on SageMaker notebook instances; also usable with SageMaker Studio's JupyterLab and Code Editor applications.
- Pricing: Follows standard Amazon EC2 P4de on-demand and reserved instance pricing; SageMaker notebook instance pricing applies on top of the underlying EC2 cost — refer to the Amazon SageMaker Pricing page for current rates.
- Instance type:
ml.p4de.24xlargeis the expected SageMaker instance type designation for this hardware configuration. - Limitation: Availability may be subject to regional capacity; users should verify instance availability in the Tokyo region console before building production dependencies on this instance type.
Related Resources
- https://aws.amazon.com/ec2/instance-types/p4/
- https://docs.aws.amazon.com/sagemaker/latest/dg/studio-updated-jl.html
- https://docs.aws.amazon.com/sagemaker/latest/dg/code-editor.html
- https://docs.aws.amazon.com/sagemaker/latest/dg/studio-updated.html
- https://docs.aws.amazon.com/sagemaker/latest/dg/nbi.html