How Much RAM Does a Smartphone Need?

Read physical DRAM, zRAM, and storage as three paths

Physical DRAM is the device total RAM that Android 17 uses when it sets a per-app limit. zRAM is compressed RAM. Storage-backed virtual memory, in the Samsung RAM Plus description, is internal storage you assign so more apps can stay open. Each path fails in a different place, and the prevention is different too.

The 8GB plus 8GB line is a label-reading example. Add the columns only after you know the second number is physical DRAM.

Rule of thumb: if a zram disk exceeds 2 times the memory it sits in, the kernel zram administration guide says there is little point in that size, because the guide expects about a 2:1 compression ratio. The same note says zram uses about 0.1% of the disk size when idle, so an oversized disk spends memory before it holds any pages. A phone listing whose virtual-memory number is larger than its physical DRAM figure sits outside that expectation. Compare the physical figure.

A 2:1 ratio still occupies DRAM

The kernel exports two counters for a zram disk. orig_data_size is the uncompressed size of data stored, in bytes. compr_data_size is the compressed size of that data. mem_used_total is the memory allocated for the disk, including allocator fragmentation and metadata, so it can sit above compr_data_size.

ratio = compr_data_size / orig_data_size

Under the guide’s expected 2:1 ratio, orig_data_size is about twice compr_data_size, so the ratio is about 0.5.

Worked example with assumed counters, chosen so the division is visible: compr_data_size = 1,000,000,000 bytes and orig_data_size = 2,000,000,000 bytes. ratio = 1,000,000,000 / 2,000,000,000 = 0.5. Those two billion uncompressed bytes occupy about one billion bytes of compressed data, and that compressed data still resides in DRAM.

Idle cost, using the guide’s own 50 MiB disksize example: 50 × 1024 × 1024 = 52,428,800 bytes. About 0.1% of that disk, while unused, is 0.001 × 52,428,800 = 52,429 bytes. That is the empty-disk overhead on the guide’s example disk.

Order from the Android 17 behavior page and the 19 August 2026 developer post: compress first, then terminate if use keeps rising. The 2:1 line is the kernel guide’s sizing expectation.

A reload records a missed cache, which is a separate fact from the gigabyte

When you leave an app, Android keeps the process cached. A later return can reuse it. If the system is low on memory, it kills cached processes. The overview also says a cached process can be terminated at any time, whatever its size. A reload records that reuse did not happen. The physical DRAM size is still a separate column on the listing.

Garbage collection is a separate stutter. The same overview says collection stops the process, and that the pause can push execution past the 16 ms threshold for smooth frame rendering. zRAM adds CPU work when pages are compressed and decompressed. Note which pause you saw before you treat it as a reason to move to a higher physical DRAM configuration. The other parts of the phone, including storage, the update window, and the screen, stay in the comparison.

Repeat one sequence with disposable data. Preserved state, a restored reload, and lost work are different results.

Takeaway: Write down whether the work survived. The reload count, on its own, does not select a DRAM size.

Stutter, a killed app, and spent storage are the ownership costs

Android 17’s behavior note names what an unbounded memory outlier does to the phone: UI stuttering, higher battery drain, and apps being killed. A killed app makes you redo the form or the edit. Stuttering shows up in the frame you were watching. Higher drain is a battery question. The battery life comparison separates stored energy from the test behind any hour. This page does not assign a watt figure to a RAM size.

Storage assigned to virtual memory is a capacity cost. Samsung’s steps have you select how much internal storage RAM Plus will use, then restart. Photos, downloads, and app data draw on that same storage. Extra physical DRAM earns its place when your own switching loses work. A larger virtual-memory number, with the same physical DRAM, does not. Read the remaining update window in the software support guide, and judge the screen in the display guide. The smartphone guides collect those checks together.

Physical memory is a package on the board. This photograph does not identify which package is DRAM. A listing that prints two RAM numbers still needs that split in writing.

When this comparison does not apply

These Android documents describe Android. An iPhone requirement needs Apple’s own listing for that model. The kernel’s 2:1 note is a sizing expectation for a zram disk in the kernel administration guide. The 4GB to 16GB+ span is the set of device configurations Google named for the per-app limits. Feature lists that name a model, a language, and a region still need that named check.

Method and sources

The pages below were fetched on 17 October 2026. A library copy of the 19 August 2026 Android Developers post was opened as well. The 2:1 ratio and the 0.1% idle note come from the kernel zram guide. The 1,000,000,000 byte counters in the worked example are assumed inputs. The 8GB plus 8GB line in the label diagram is an example of how to split a listing, not a handset.

• Android Developers Blog, 19 August 2026: Preparing your app for broader memory limits
• Android 17 behavior changes: App memory limits
• Overview of memory management, last updated 2026-05-19
• Kernel zram administration guide
• Samsung: What is RAM Plus and how to use it, last updated 14 December 2022