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!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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