Home
Exploring MMCloud Features
WaveRider
When enabled, WaveRider allows OpCenter to optimize cloud resources by moving jobs as the resource demands change.

Introduction
Background
Getting Started
Working with OpCenter
Exploring MMCloud Features
- SpotSurfer
  SpotSurfer removes the risk of running stateful applications on Spot Instances while reducing costs significantly.
- WaveRider
  When enabled, WaveRider allows OpCenter to optimize cloud resources by moving jobs as the resource demands change.
  - Manual Job Migration
    Running jobs can be moved manually at any time using the CLI or the OpCenter web interface to change, for example, the compute platform or the pay type.
  - Policy-driven Job Migration
    When enabled, WaveRider uses a rules-based policy to determine when to migrate a job to a different virtual machine.
  - Programmatic Job Migration
    Initiate job migration by inserting the float migrate command into the job script.
- SurfZone
  SurfZone is a cost management feature that helps limit the amount spent on cloud computing each month.
- Gateway Service
  The gateway service provides a reverse proxy so that a job can migrate from one host to another without interrupting client connections.
- WaveWatcher
  WaveWatcher displays real-time resource utilization graphs on a per job basis.
Working with Applications
MMCloud Reference Guides

WaveRider

When enabled, WaveRider allows OpCenter to optimize cloud resources by moving jobs as the resource demands change.

Feature Description

Resource utilization (CPU, memory and storage) is not constant while a job runs. Users face a difficult choice: over-provision and overpay, or under-provision and risk out-of-memory conditions. With WaveRider, users can start with a small virtual machine (VM) and dynamically migrate to bigger VMs (and back down to smaller VMs) as the application demands change during a complete job run.

Job migration is initiated in three ways:

Manual: migration initiated using CLI commands or the OpCenter web interface.
Policy-driven: migration triggered by rules-based policy configured per job (policy based on CPU and memory utilization thresholds).
Programmatic: migration executed at specific program breakpoints defined by job script.