Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.canton.network/llms.txt

Use this file to discover all available pages before exploring further.

This section was copied from existing reviewed documentation. Source: docs/src/validator_operator/validator_hardware_requirements.rst Reviewers: Skip this section. Remove markers after final approval.
This section describes hardware requirements for running a validator. Note that these are reference values. Actual requirements can vary based on usage of your validator. We recommend monitoring your production validator nodes with respect to CPU and memory usage of all components and disk usage of the database, and adjust the resourcing as needed. The requirements include both the validator and participant container. These requirements are largely identical between the docker-compose based deployment and the k8s deployment but exclude overhead from k8s itself or ingress.
UsageCPUsMemoryDB CPUsDB MemoryDB size
Experiments on local laptop or minimal VM16GB11GB1GB
Production validator with little activity28GB24GB10GB
Production validator for an app provider with moderate activity216GB24GB100GB

​
Database Latency

Components are relatively sensitive to database latency. If you use a managed database offering like GCP CloudSQL, it is recommended that you allocate it in the same region and zone that your cluster runs in.