Appendix: AWS deployment guidelines

Recommended instance types

As a general guideline, we recommend:

• Processor Type: ARM-based CPU

• Sizing:

  • If spill-to-disk is not enabled: 1:8 ratio of vCPU to GiB memory

  • If spill-to-disk is enabled (Recommended): 1:16 ratio of vCPU to GiB local instance storage

When operating in AWS, we recommend the following instances:

Starting in v0.3.1, the Materialize on AWS Terraform uses ["r7gd.2xlarge"] as the default node_group_instance_types.

Locally-attached NVMe storage

For optimal performance, Materialize requires fast, locally-attached NVMe storage. Having a locally-attached storage allows Materialize to spill to disk when operating on datasets larger than main memory as well as allows for a more graceful degradation rather than OOMing. Network-attached storage (like EBS volumes) can significantly degrade performance and is not supported.

Starting in v0.3.1 of Materialize on AWS Terraform, disk support (using OpenEBS and NVMe instance storage) is enabled, by default, for Materialize. With this change, the Terraform:

• Installs OpenEBS via Helm;

• Configures NVMe instance store volumes using a bootstrap script;

• Creates appropriate storage classes for Materialize.

Associated with this change,

• The following configuration options are available:

  • enable_disk_support
  • disk_support_config

• The default node_group_instance_types has changed from "r8g.2xlarge" to "r7gd.2xlarge". See Recommended instance types.

CPU affinity

It is strongly recommended to enable the Kubernetes static CPU management policy. This ensures that each worker thread of Materialize is given exclusively access to a vCPU. Our benchmarks have shown this to substantially improve the performance of compute-bound workloads.

TLS

When running with TLS in production, run with certificates from an official Certificate Authority (CA) rather than self-signed certificates.

See also

• Configuration
• Installation
• Troubleshooting