Re: diego questions: default memory and passing env variables

Matthew Sykes <matthew.sykes@...>

Memory limits are set via cf scale.

`cf scale <app-name> -m 512M`

will scale your app to 512MB per instance. The cli will then tell you to
restage your application so the buildpacks can observe the new limit and
make the necessary changes. At one time, this was especially true of the
java buildpack.

On Wed, Sep 2, 2015 at 6:08 PM, Siva Balan <mailsiva(a)> wrote:

We are not using Diego and we are on CF version 211.
I had my application started with 2GB of memory set in the manifest file.
I then ran the following command and restaged the app:
cf set-env <app-name> MEMORY_LIMIT 1024m
Then when I ran "cf app <app-name>", it was still showing the instance
memory of 2GB but the heap size allocated to the application was cut in
half and I confirmed this through New Relic app. Also, the first full GC of
the app occurred when the memory of the instance was at 1.3GB. So I am not
quite sure of the description of the MEMORY_LIMIT env variable as described
I did not see my application restart when the instance memory went over
Any ideas about this behavior?


On Tue, Sep 1, 2015 at 7:40 PM, Amit Gupta <agupta(a)> wrote:

Responses inline.

On Tue, Sep 1, 2015 at 7:13 PM, Tom Sherrod <tom.sherrod(a)>

What is the default memory size of an app deployed in diego? cf apps
indicate 1GB.
Yes. This isn't a diego thing, this is a CC thing.

cf set-env doesn't appear to be getting the environment variable
information to the running container. Is cf set-env the correct method to
You likely need to restage the application for ENV var changes to take
effect. Unless I'm mistaken, this too is not diego-specific, and applies
to DEA containers as well.

Matthew Sykes

Join to automatically receive all group messages.