Determine cause of high memory consumption

Is this still relevant? It's been almost 10 years since the last update and a lot has changed since then. It's always great to profile and reduce memory consumption, but it's unclear exactly where this issue is headed. Marking PMNMI for anyone involved to provide direction / next steps.

There are a few issues covering most of what's in here either recently fixed or in progress:

In terms of this installer, 📌 Add the ability to install multiple modules and only do a single container rebuild to ModuleInstaller Active made a big difference.

One possible next step for reducing memory usage in the installer/module installs would be 📌 Add a core FileCache implementation that is database-backed Active , that would heavily reduce the cost of plugin discovery because it would be built incrementally as more modules are installed. We also have 🌱 Reduce memory/cpu/io cost of attribute discovery Active open more generally.

Smaller views data issue 📌 ViewsViewsData loads all actions multiple times unnecessarily Active .

Bigger views data issues 🐛 ViewsData should not cache by language Needs work and 📌 Allow fields to be opted out of views data Active

Also 🐛 RoutePreloader loads a lot of routes Active , that is a considerable chunk of memory savings there. Need to get back to it and summarize the current state. I think it's fine to not keep this issue as a meta.

Maybe install system is a better home for this