During the transition to using settings for "container memory" in each back-end module's default LaunchDescriptor (
FOLIO-1729 FOLIO-2185) instead of using folio-ansible group_vars to specify -Xmx Java option ( FOLIO-2241 FOLIO-2242), we needed to temporarily raise the container memory allocation to 130% of the old -Xmx setting ( FOLIO-2250).
FOLIO-2358 is now in progress to use new JVM features to manage container memory. After each module is upgraded (see each ticket linked from FOLIO-2358) then it will be utilising 66% of the LaunchDescriptor "Memory" setting for the Java heap allocation, leaving the remainder for other stuff.
So after each is upgraded, then the next step is for the developers of each back-end module to determine the default container Memory allocation, and adjust their configuration.
At ModuleDescriptor path: $.launchDescriptor.dockerArgs.HostConfig.Memory
As noted there, these levels are appropriate for running a basic system such as the "folio-snapshot-load" reference environment and the Vagrant VMs. So this default container memory setting should be as low as possible.