Summary of "Los juegos malgastan memoria RAM a propósito"

Core argument

Many modern games deliberately use more RAM than strictly necessary. Tight optimization of asset sizes and streaming systems costs time and money, so developers often trade finer memory efficiency for faster, cheaper development and fewer bugs — assuming most players have enough RAM.

What RAM does (analogy)

RAM is the CPU’s workbench: it holds the assets and intermediate data the game needs to run quickly. If the workbench is too small, the system falls back to slower disk access and stutters.

A few extra points:

VRAM (GPU memory) holds textures for rendering, but texture loading and management still go through main RAM and often keep copies or intermediate data there.
Insufficient RAM forces more frequent disk reads and can cause frame drops, hitching, or longer load times.

Which assets use the most RAM

Textures are by far the biggest consumer of RAM:

Modern textures are not single images; they include multiple associated maps (normal/height, metallic/smoothness/roughness, etc.), which multiplies memory use.
Artists often create very high-resolution source textures and then downscale for in‑game use. Producing and verifying multiple resolutions per texture is labor-intensive.
GPUs support compressed texture formats that reduce memory, but those must be chosen carefully to avoid visible quality loss.
Example: In How’s Legacy a small cat uses a 4096×4096 main texture and a 1024×1024 eye texture — likely overkill for typical viewing distances.

Other asset considerations:

3D meshes/models are relatively small (lists of vertices and polygons). A character’s filesize is often dominated by textures rather than the mesh.
Game code and engine binaries consume comparatively little RAM; micro-optimizations like shortening variable names are irrelevant for memory usage.
Sound: short effects can be fully loaded into RAM, but long music or ambient tracks should be streamed to avoid wasting memory.

Common places where RAM balloons

Open-world streaming: to avoid pop-in or errors, teams may load larger-than-necessary map regions “just in case,” increasing RAM usage. Proper margin and tile streaming requires extra QA and engineering.
Game engines: general-purpose engines (Unity, Unreal, Godot) speed development but introduce a large, generic runtime structure into RAM. Even if some subsystems are disabled, the engine brings baseline scaffolding that increases memory use versus a small custom engine.

Practical optimization strategies

Right-size textures: ship smaller resolutions where high detail is unnecessary (use mipmaps and LODs tied to view distance).
Use GPU-compressed texture formats where acceptable to save VRAM and main RAM.
Stream long audio (music/ambience) instead of preloading full tracks.
Implement smarter world/scene streaming to load only necessary regions on demand.
Disable or strip unused engine subsystems where feasible to reduce baseline memory.
Balance optimization effort against development cost and target hardware — optimize where it yields the most benefit.

Context / industry tradeoffs

Optimization is costly in both time and money; many studios accept “good enough” RAM usage to shorten schedules and lower risk.
During hardware shortages or on lower-end targets teams can prioritize optimizations, but shifting priorities is a business decision and not always guaranteed.

Other mentions (resources, sponsor, extras)

Sponsor product: Libernovo UFO ergonomic chair

Electronics-driven adaptive Flexfit backrest with eight panels
Multiple recline positions (105°–160°)
5-minute stretching/massage mode
Adjustable seat height (~11.2 cm), adjustable neck support, multi-directional armrests
Optional foot rest; Kickstarter-backed

Main speakers / sources

Narrator / channel: Guinchu (video host)
Game example: How’s Legacy (used to illustrate oversized textures)
Engines referenced: Unity, Unreal Engine (referred to as “Real Engine” in subtitles), Godot
Sponsor/product: Libernovo UFO (chair)