NIAD-3110: mhs resource assignment recommendation

[ORybak5]

What

MHS Adaptor resource assignment recommendation

Why

It is good to provide some guidance in terms of resource expectation

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Internal change (non-breaking change with no effect on the functionality affecting end users)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have updated the Changelog with details of my change in the UNRELEASED section if this change will affect end users

[adrianclay]

Would this not live better under the mhs/operating-mhs-adaptor.md file which is linked below under the title "Operational Considerations"?

[adrianclay]

Also "heap space" is a Java term, I don't think we're expecting our users to be Java experts or knowledgeable about this at all. I think our guidance should be in terms of Docker (which we do expect our users to be familiar with).

[ORybak5]

ok, I will adjust the terminology to remove Java specific names.