# What 32 GB per GPU changes for a remote graphics project

WorkSpaces G7 specifies 32 GB per GPU. Scene residency, temporary buffers and multi-device behavior determine whether that budget suits a graphics project.

Author: Retrivium editorial team
Language: en
Analysis published: 2026-11-03
Event date: 2026-09-16
Original announcement: https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-workspaces-nvidia-blackwell-gpu-instances/
Canonical URL: https://retrivium.ai/retrospectives/retro-workspaces-g7-scene-memory/

The useful memory statement in the WorkSpaces G7 release is 32 GB per GPU. A bundle with more devices does not, by that wording alone, promise a single larger framebuffer for one scene. The application decides how separate device memories are used.

## Read the denominator

The [September 16, 2026 announcement](https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-workspaces-nvidia-blackwell-gpu-instances/) describes RTX PRO 4500 Blackwell Server Edition GPUs with 32 GB GDDR7 each and bundles containing one or two GPUs. The denominator is a device, not an arbitrary application allocation.

That distinction matters for a remote graphics project with large textures, geometry and temporary buffers. Adding devices can support a different execution strategy, but a renderer that replicates scene data still has a per-device constraint. The bundle specification does not identify which strategy an application uses.

## Hardware introduction was an earlier milestone

[NVIDIA introduced Blackwell RTX PRO on March 18, 2025](https://nvidianews.nvidia.com/news/nvidia-blackwell-rtx-pro-workstations-servers-agentic-ai). This supplied the professional hardware context before the WorkSpaces integration. It did not certify the memory behavior of every design or rendering program later delivered on that hardware.

The causal hypothesis is that larger device budgets can remove some scene constraints while leaving application architecture decisive. This is not a claim that a particular customer scene fits, nor an independent performance comparison with an older generation.

## Remote graphics already had a predecessor

The [July 17, 2025 AppStream G6 release](https://aws.amazon.com/about-aws/whats-new/2025/07/amazon-appstream-2-0-support-gpu-based-instances/) established an earlier L4-based application-streaming option. Its existence shows that remote delivery and GPU generation evolve separately. The later Personal/Core bundle does not retroactively change the earlier service's memory contract.

A migration argument should therefore name both the application delivery model and the resource shape. “Newer GPU” is not a sufficient description of whether an existing project can open, render and save correctly in the intended remote session.

## A scene budget rather than an aggregate total

An illustrative project sheet can distinguish:

| Component | Why it belongs in the budget |
| --- | --- |
| Persistent scene data | Geometry and textures remain resident |
| Temporary render buffers | Peak use can exceed the idle scene |
| Display and application state | The desktop consumes resources too |
| Multi-device behavior | Replication and partitioning differ |

The sheet records categories, not invented memory measurements. The important evidence is a representative scene at its demanding stage, rather than an empty application reporting unused memory. A successful file open may precede a later allocation peak.

## The historical significance

G7 expanded the device budget available within a particular desktop service. It did not abolish per-device accounting or establish that two GPUs act as one memory pool. A clear migration report keeps hardware capacity and application allocation behavior separate.

[VRAM and models](/journal/vram-and-models/) develops the same denominator problem for inference. [Render-farm idle GPUs](/journal/render-farm-idle-gpus/) explains why rendering workloads need their own resource description. Those connections make the announcement useful without turning a memory specification into a universal project-fit guarantee.