Hey irfanhabib!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

@irfanhabib Why is the memory so high for this? In order to deploy Stratos HA we need about 9GB because we're deploying 3 instances at 1.5GB while running the previous 3x1.5GB instances. Is there a particular reason the memory is so high? When looking at the output of cf app stratos I'm seeing it not using much memory at all when idle 8.8M of 1.5G but then when a single user is on the app, I see it spike to 31.1M of 1.5G.

@rogeruiz Unfortunately, CF currently doesn't support providing separate memory limits for deploying an app and when its deployed. We require significant amounts of memory when we're building the app (Since building an angular2 app is a memory intensive process). While we don't require much while its running. The app is built when you do a cf push.
The memory limit can be scaled down after the app has been pushed, using the cf CLI.

Ah perfect. That's what I arrived to with some sleuthing in CF Slack. Thanks @irfanhabib. Would it make more sense to build the app before deploying it? Maybe I can help with that. Also, is there a way to load test what memory limits it requires when it's running besides having a few dozen people clicking around the interface?

@rogeruiz We've gone back and forth on this, but generally we believe its a good idea to have the entire app built when we perform a cf push. Partially building the app before a push, is against the principle of cf push (where the application being pushed should be built using a buildpack).

Any thought @nwmac?

@irfanhabib, what if we leverage cf-dockerized-buildpacks? https://github.com/18F/cf-dockerized-buildpack

Or at bare minimum I could write up some docs on what the size should be after the deployment?

RE:

Also, is there a way to load test what memory limits it requires when it's running besides having a few dozen people clicking around the interface?

@rogeruiz I agree we should document what the min. size should be after a deployment.

Also, is there a way to load test what memory limits it requires when it's running besides having a few dozen people clicking around the interface?

We don't have any mechanism yet to load test the app.