On consumer CPE, the bill of materials is won or lost in a handful of components, and DRAM is one of the largest. The received wisdom has been that a modern RDK-V box needs 2 GB of RAM to run comfortably with streaming apps. This platform does not: a complete RDK-V stack running some premium apps – Amazon Prime Video and YouTube – in just 1 GB of RAM – with 4K video now playing in the YouTube app.
What 1 GB has to hold
Fitting a real deployment into 1 GB means nothing gets to be careless about memory. Running at the same time, inside that budget, are:
- The RDK-V stack and WPEFramework
- The customer UI
- Premium apps – Amazon Prime Video and YouTube – with their DRM-protected (PlayReady) playback
Holding all of that inside 1 GB means treating memory pressure as a first-class design constraint – WPEFramework footprint, UI memory, DAC (Downloadable Application Container) tradeoffs, and the memory behaviour of DRM and EME during playback all have to be measured and kept in budget, not left to chance.
Why the DRAM tier is a commercial decision
At current DRAM prices, the gap between a 1 GB and a 2 GB BOM is significant at volume. A platform that runs the premium apps users expect, at 1080p, in 1 GB is money saved on every unit shipped – and without stripping the box’s features down to get there. The saving comes from engineering, not from cutting features.
4K video in 1 GB, with the UI still live
The latest result pushes this further: on a 1 GB Hi3798MV200 platform, the YouTube app plays 4K video – and the full resident UI stays up throughout. It is the same UI build that runs on the 2 GB platform, unmodified and not offloaded, so the box keeps responding: on-screen notifications and overlays (volume up, volume down, mute) remain active while 4K is playing. Fitting a 4K decode pipeline and a live, resident UI together inside 1 GB is exactly the memory-pressure engineering this work is about. More on the consulting offer is on the Services and Use Cases pages.