proof-server:proof-server-configuration

To configure proof server workers and job capacity for production, set the num-workers CLI flag to match available CPU cores and apply a job-capacity limit to control queue size and prevent throughput bottlenecks.

The best way to set Docker memory limits for a proof server deployment is to apply an appropriate Docker memory constraint alongside worker scaling and job queue limits to prevent memory exhaustion and ensure reliable runtime behavior.

Proof server CLI flags map directly to corresponding environment variables, allowing you to apply consistent configuration and runtime tuning across development, CI, and Docker container deployments without modifying startup commands.

Your proof server may have a slow startup time in CI due to parameter prefetching tradeoffs; tuning the prefetching behavior and worker sizing can optimize expected startup time and support capacity planning.

Yes, proof server configuration supports job timeouts for resource planning, allowing operators to control runtime behavior and prevent long-running proving jobs from exhausting system resources in production environments.

You can apply proof server configuration across environments, but specific deployment profiles prescribe different recommended settings for development, CI, and production to properly tune workers, job capacity, and Docker memory constraints.