What this means
What this means
The two cases work differently, because before your machine exists there is nothing to resize and nothing has been paid. After it exists, a size change is a real change to a real machine.
Before you start
Before you start
Know which case you are in. If your order still shows as queued or awaiting build, it has not been built yet.
Step-by-step guidance
Step-by-step guidance
- Before it is built: open the Java VM page in the portal, find your request in the list, and change the size in the dropdown. It applies at once and costs nothing.
- After it is running: open the service in the portal and use Upgrade your Java VM size.
- Pick the size you want. The price shown is the difference from what you already pay, not the full price of the new size.
- Pay by mobile money, card or PayPal, as with anything else.
- We will contact you to agree a time for the change.
- At the agreed time the machine gets more vCPU, memory and disk, and restarts once.
What CM Cloud support will review
What CM Cloud support will review
Support will confirm the new size suits what your application is actually doing before scheduling it — a bigger machine does not help an application that is waiting on a database.
What is not automated yet
What is not automated yet
Resizing a running machine is not instant and is not silent. It needs a restart, so we agree a time with you rather than doing it the moment payment clears. If your application does not size its heap from the machine, we will tell you what to change so the extra memory is actually used.
Safety note
Safety note
Your data, your domain and your certificate are untouched by a resize. The only visible effect is one short restart at a time you agreed.
Safe next action
Safe next action
If your order is still queued, change the size yourself on the Java VM page. If your machine is running, open its service page and choose the size you need.