Documentation

Performance upgrade preview

Private preview beta

The performance upgrade preview is available to InfluxDB 3 Enterprise Trial and Commercial users as a private beta. These features are subject to breaking changes and should not be used for production workloads.

To share feedback on this preview, see Support and feedback options. Your feedback on stability and performance at scale helps shape the future of InfluxDB 3.

InfluxDB 3 Enterprise includes a private preview of major performance and feature updates. These updates represent the foundation for the upcoming 3.10 and 3.11 releases. Available in beta now for InfluxDB 3 Enterprise, many of these improvements will be coming to InfluxDB 3 Core in subsequent release cycles.

Key improvements

  • Faster single-series queries: Optimized data path for fetching specific trends over long time windows, with single-digit millisecond response times.
  • Consistent resource usage: Reduced CPU and memory spikes during heavy compaction or ingestion bursts through key-range partitioning.
  • Wide-and-sparse table support: Handles schemas with up to hundreds of thousands of columns and dynamic schema evolution without expensive rewrites.
  • Automatic distinct value caches: Dramatically reduced latency for metadata queries like SHOW TAG VALUES in InfluxQL.

Enable the preview

Add the --use-pacha-tree flag to your normal influxdb3 serve startup command:

influxdb3 serve \
  --node-id host01 \
  --cluster-id cluster01 \
  --object-store file \
  --data-dir ~/.influxdb3 \
  --use-pacha-tree

The flag exposes additional configuration options prefixed with --pt-. See Configure the preview for tuning options, or Monitor the preview for system tables and telemetry.

Who should try the preview

Consider enabling the preview in your staging or development environment if you have workloads with high cardinality, wide tables, frequent backfill, or query-heavy access patterns.

Your feedback on stability and speed at scale helps inform the development of features planned for general availability in the 3.10 and 3.11 releases.

Important: Upgraded file format

These upgrades use a new file format (.pt files). When you enable the preview, your existing data is automatically upgraded to the new format in place. While downgrading is possible, any data written after the upgrade will not be included in the downgrade.

Systems with large amounts of data may take longer to complete the conversion. For the beta, we recommend starting with a fresh setup for testing and evaluation rather than converting existing data.


Was this page helpful?

Thank you for your feedback!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a private preview of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a private preview of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

New in InfluxDB 3.8

Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

See the Blog Post

InfluxDB 3.8 is now available for both Core and Enterprise, alongside the 1.6 release of the InfluxDB 3 Explorer UI. This release is focused on operational maturity and making InfluxDB easier to deploy, manage, and run reliably in production.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On April 7, 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