JDK 11+ has support for dynamically adding compiler threads base on available memory. The runtime call to os::available_memory() uses the OSContainer API in order to see what the available memory is. In a container setting, especially with small memory/cpu limits this setting might be contra-productive. Reading available memory via the cgroup interface files for no good reason. We should consider turning UseDynamicNumberOfCompilerThreads off in our JDK 11+ images and allowing for users to turn it on should they need to.

More experimentation needed.