Hardware requirements for Dynatrace Monaco CLI

Latest Dynatrace
Reference
5-min read

This page provides an overview of the hardware requirements for Dynatrace Configuration as Code via Monaco.

Required memory

Set reasonably high memory limit or ensure swap space is available

When executing in a container with a hard memory limit or limited physical hardware, make sure to set a reasonably high memory limit or ensure that swap space is available.

The required memory is mostly defined by the number of configurations and the size of their JSON template files.The following tables give you an idea of memory requirements for sample project sizes; your project might need more or less memory.

High memory requirement for CLI version 2.9.0 and earlier

Dynatrace Monaco CLI version 2.9.0 and earlier has higher memory requirements.

Dynatrace Monaco CLI version 2.9.1+

Project size / Number of configurations	Storage size on disk MB	Required memory (RAM+swap) MB
125	0.8	5
625	3.2	15
2500	12.8	40
5000	25.5	80
10000	50.9	160
25000	127.3	310
50000	254.5	600
100000	509	1200

For larger projects, follow these rules for estimating the required memory for a deployment:

The available memory needs are around 2.5 times larger than the storage required by your configurations on disk.
Around 15kB of memory is required per configuration in your project.

Configure memory limits

Setting the GOMEMLIMIT environment variable can define a soft memory limit for the Dynatrace Monaco CLI. For more details, see the GoMemLimit documentation.

GOMEMLIMIT is a numeric value with an optional unit suffix of B, KiB, MiB, GiB, or TiB. If no suffix is supplied, the value is assumed to be in bytes (B).

CPU impact on deployment times

Available CPU mostly impacts deployment time needed and, unlike memory, doesn't impose hard limits. On more limited hardware, deployments take more time.

For example, deploying from a container limited to a single vCPU takes significantly longer than one with several available vCPUs or running directly on a system with a multi-core processor.

The following tables give a rough overview of how the number of configurations impacts deployment times. This merely illustrates the relationship between project size and deployment time and probably won't match deployment time on your specific hardware.

With Dynatrace Monaco CLI version 2.7.0+, the deployment times are measured for parallel deployments, which are available by default.
With Dynatrace Monaco CLI version 2.6.0 or earlier, deployment is fully sequential and therefore notably slower than with newer versions.

Dynatrace Monaco CLI version 2.7.0+

This table demonstrates that deployment time doesn't grow linearly with the size of your projects. This is because of the behavior of the Dynatrace API as the number of requests and existing configurations increases—this causes increased rate limiting and processing time when adding configurations.

Project size / Number of configurations	Estimated deployment time
125	20 s
625	35 s
2500	2 min 30 s
5000	3 min 45 s
10000	10 min
25000	50 min