VM Sizes and Storage

Applies to: all AppWizzy hosted VM projects

A machine size defines the CPU, memory, and hosting rate for a VM. The selected template defines the available machine sizes.

The template also defines the active disk allocation when it has a specified disk size.

What a machine size controls

Each machine size provides these resources:

  • virtual CPU capacity.
  • memory capacity.
  • a hosting rate for each active 24-hour period.

More CPU can improve parallel processing and compute-heavy work. More memory can support larger applications, databases, desktop tools, and development processes.

A larger machine does not automatically change the installed template or application. It also does not replace the active disk.

Available sizes depend on the template

AppWizzy shows only machine sizes that meet the selected template requirements. A resource-intensive template can require a larger minimum size.

Review the live creation interface before you create a project. It shows the current eligible sizes, resources, and hosting rates.

You cannot select an ineligible size for the template.

Active disk storage

The active disk stores the persistent state of the VM. Depending on the template, this state can include:

  • application code and configuration.
  • databases and uploaded files.
  • installed packages and tools.
  • terminal files and shell history.
  • browser profiles and sessions.
  • workspace files and generated output.

The project or pricing interface shows the disk size when the template has a specified allocation.

The machine size and disk allocation are separate settings. Selecting more CPU or memory does not increase the disk allocation.

AppWizzy does not provide a standard disk resize control. Review the displayed disk allocation before you create the VM.

Data persistence

The active disk survives these operations:

  • pause and resume.
  • VM restart.
  • CPU and memory resize.

A restart or resize can stop running processes. Save work to the active disk before you start either operation.

Data that exists only in memory can be lost. Deletion removes the VM and its active disk.

Read Data Persistence and Backups before a destructive action.

Resize a VM

Use the machine setting on the project page when resize is available.

  1. Confirm that the VM is ready.
  2. Select an eligible machine size.
  3. Review the new hosting rate.
  4. Confirm the resize.
  5. Wait for the VM to become ready again.
  6. Check the application and required services.

AppWizzy stops the VM, changes its CPU and memory, and starts it with the same active disk.

The VM is unavailable during this operation. Subsequent hosting periods use the selected machine rate.

Choose a suitable size

Start with the smallest eligible size that supports your expected workload. Select more resources for these workloads:

  • graphical desktop applications.
  • several active development services.
  • memory-intensive builds or package installation.
  • larger databases or application traffic.
  • concurrent agent or automation work.

Monitor the application after launch. Resize the VM when resource limits affect normal work.