Documentation

Simulate a production-like load

With your schema defined you can begin to simulate a production-like load that writes data to your InfluxDB cluster. This process helps to ensure that your schema works as designed and that both your cluster’s scale and configuration are able to meet your cluster’s write requirements.

We do not recommend writing production data to your InfluxDB cluster at this point.

Load testing tools

Contact your InfluxData sales representative for information about load testing tools. These tools can simulate your schema and desired write concurrency to ensure your cluster performs under production-like load.

Use your own tools

You can also build and use your own tools to load test a production-like workload. Use Telegraf, client libraries, or the InfluxDB API to build out tests that simulate writes to your cluster.


Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2