Latency spikes in Terramate orchestration during concurrent stack runs

When executing Terramate orchestration commands against multiple Terraform stacks in parallel, the observed latency grows disproportionately compared to running the same stacks sequentially.

The goal is to determine whether this latency originates from Terramate’s internal templating or dependency‑resolution layers, the Go runtime’s concurrency handling, or downstream Terraform invocations, while considering variations between the open‑source CLI and managed cloud offerings and the size of the dependency graph.

What specific component of Terramate introduces contention under concurrent execution? Does the templating step cause serialized file‑system access that scales with stack count? Are there configuration flags or architectural adjustments that can reduce this latency without sacrificing correctness?