---
title: "Cluster | Speedscale Docs"
description: "Configure infrastructure settings for Speedscale by adjusting log levels, build tags, and resource limits to optimize performance during API testing."
canonical: "https://docs.speedscale.com/reference/configuration/cluster/"
---

[Documentation index](https://docs.speedscale.com/reference/llms.txt) | [Markdown](https://docs.speedscale.com/reference/configuration/cluster/index.md) | [Canonical page](https://docs.speedscale.com/reference/configuration/cluster/)

# Cluster

The Cluster section is used for setting up infrastructure-related configurations. This includes specifying the log level, build tag, and resource limits for both the Generator and Responder components.

<a id="generator-service-account"></a>

## Generator service account

`generatorServiceAccount` runs the generator as an existing service account in the replay namespace instead of the one Speedscale creates, so the generator carries that account's cloud workload identity. The account must match a selector in the operator's Helm values. See [Run the generator as your own service account](https://docs.speedscale.com/guides/replay/generator-service-account/).

# Container resource warnings

![container-resouce-warning](https://docs.speedscale.com/assets/images/container-using-95percent-resources-warning-32f44f37ff0057a6352ffd81a1f4651f.png)

Speedscale introduces additional load during testing, which can lead to higher resource consumption, particularly in terms of CPU and memory.

<a id="impact"></a>

### Impact:

*   Lower throughput than expected.
*   Potentially not reaching the desired Transactions Per Second (TPS) from your test configuration.

<a id="solution"></a>

### Solution:

Increase your container's resource limits to accommodate the additional load generated by Speedscale.
