Quick Base Memory Calculations

This all makes sense, though it becomes difficult to 'trace' where heavy fields are causing utilization issues.  It would be awesome to have an admin tool that could loop through a source field, all of it's uses, and come back with an impact statement for that field... such as total RAM consumed from this field and all of it's derivatives... possibly listing the RAM consumed for each usage on the field usage tab.  It's very difficult for developers to put a finger on which fields are causing the most consumption in a given app without extensive research and computation outside of the application.  This type of solution would empower developers to design within the limits of an allotted app and explore alternative solutions that are possibly not as RAM intensive but yield the same results for end users.