Hi, thanks for your work on the documentation. I thought I'd offer some comments from

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

cf scale questions about docs-dev-guide HOT 3 CLOSED

cloudfoundry commented on July 23, 2024

cf scale questions

from docs-dev-guide.

cf-gitbot commented on July 23, 2024

We have created an issue in Pivotal Tracker to manage this:

The labels on this github issue will be updated when the story is started.

from docs-dev-guide.

ljarzynski commented on July 23, 2024

@johnyesberg Thanks for filing this issue.

@dkoper Would appreciate your help on answering these questions if you are able.

from docs-dev-guide.

dkoper commented on July 23, 2024

@ematpl or @zrob can confirm the details, but I'll take a first stab:

-i, cf may remove some of my instances - I believe it stops and removes the instances with the highest index number (each app instance has an index number, as listed in cf app your-app).
This article explains how your app instance is stopped.
-m and -k currently need an app restart to take effect. cf scale will prompt for confirmation unless -f is used.
It is the memory made available to the app container, so is shared by the OS, JVM and anything else that may be running inside. Java Buildpack 3.1 and higher calculate how much memory can be assigned to the VM (like -Xmx) at container startup time. (In versions before that, it was calculated at staging time so required a restage for changes to take effect).

from docs-dev-guide.