That doesn't matter. The textures will be loaded no matter what once accessed, it doesn't matter what those textures are loaded and stored for. The textures for the Sundial are loaded and stored only when you access the Sundial. And once you leave the Sundial the RAM used for those textures is released to be used for other processes. So removing content has little to no effect on RAM because ram is used for current processes. And a current process is something currently going on, so if you're not accessing something it's not a current process and not stored in RAM.

[quote][quote]No. What do you think gets stored in ram?[/quote] Big texture files are the usual culprit, in addition to actual executables and resident services.[/quote] Textures are pre loaded into VRAM, not regular RAM. While consoles use system RAM and VRAM as the same thing, there's only a certain amount preallocated so VRAM won't interfere with regular RAM. (Destiny barely uses 3GB of RAM on my system, I'm assuming console sees a similar experience. Executables are windows file types and are responsible for launching applications. (Not specific to windows, used windows as an example) Wth is a resident service? Games do not use that term at all.