Workload Manager best practices for Redis

Instances in the evaluation scope must have the Google Cloud Agent for Compute Workloads configured to run Workload Manager evaluations. If you have not configured the agent correctly, evaluation results can be incomplete or inaccurate. The minimum recommended version is 1.2.

To ensure that the VM restarts automatically in the event of a failure, enable the Compute Engine automatic restart policy for any VM that is running a Redis workload.

The default provisioned IOPS and throughput values for small Hyperdisks can be too low to guarantee proper performance. We recommend that you raise these values to a minimum of 10,000 IOPS and 1 GiB/s throughput.

For more information, see Default performance.

To prevent any platform maintenance events from stopping or restarting a VM that is running Redis workloads, the onHostMaintenance parameter for the VM must be set to the recommended option MIGRATE.

For more information, see Set VM host maintenance policy.

Google Cloud recommends that you do not run Redis workloads on PD Standard and Hyperdisk Throughput disk types, because these are hard disk-based disks and might lead to degraded performance.

For more information, see Persistent disk types, Hyperdisks, and Hyperdisk Throughput.

To maintain proper high availability, we strongly recommend that you send your replication to a machine in a different zone or region from the primary location.

For more information, see Well-Architected Framework: Reliability pillar.

Persistence ensures that the system writes the data sent to the primary instance to a durable storage. In a replicated system, choosing the right persistence strategy is critical to prevent data loss in case of a failure. If you choose not to use any persistence options, Google Cloud recommends that you disable the systemd Redis service from automatically restarting to avoid potential data integrity issues.