Skip to content

docs(enterprise): add cross-references to performance preview #7049

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jstirnaman merged 2 commits into from
Apr 2, 2026
Merged

docs(enterprise): add cross-references to performance preview #7049

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b796e21
docs(enterprise): add cross-references to performance preview overview
jstirnaman Apr 2, 2026
de670e0
docs(enterprise): clarify "Why these upgrades" intro wording
jstirnaman Apr 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions content/influxdb3/enterprise/performance-preview/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
---
title: Performance upgrade preview
seotitle: Performance upgrade preview for InfluxDB 3 Enterprise
Expand Down Expand Up @@ -38,13 +38,13 @@

## Why these upgrades

The existing storage layer in InfluxDB 3 was built around Apache Parquet and
optimized for analytical workloads.
The existing InfluxDB 3 storage layer uses [Apache Parquet](https://parquet.apache.org/)
and is optimized for analytical workloads.
Customers running high-cardinality, wide-schema, and query-intensive workloads
need better single-series query performance, more predictable resource usage,
and the schema flexibility that made InfluxDB v1 and v2 popular.
These upgrades address those gaps while maintaining full compatibility with
InfluxDB 3's data model and query languages.
These upgrades extend the storage layer to support those workloads while
maintaining full compatibility with InfluxDB 3's data model and query languages.

Key improvements include:

Expand Down Expand Up @@ -111,7 +111,8 @@

Data is stored in a new columnar file format (`.pt` files) optimized for
time-series workloads.
All data within a file is sorted by column family key, series key, and
All data within a file is sorted by column family key,
[series key](/influxdb3/enterprise/reference/glossary/#series-key), and
timestamp, which enables efficient compaction, querying, and filtering.

The format uses type-specific compression algorithms that adapt to data
Expand All @@ -126,7 +127,7 @@
Fields in the same family are stored together on disk.
For wide tables with hundreds of fields, this dramatically reduces I/O.

When writing line protocol, use the `::` (double-colon) delimiter in field
When writing [line protocol](/influxdb3/enterprise/reference/line-protocol/), use the `::` (double-colon) delimiter in field
names to assign fields to a family.
The portion before `::` is the family name; everything after is the field name.

Expand Down Expand Up @@ -158,8 +159,10 @@

### Bounded compaction

Incoming writes are buffered in the WAL, flushed to snapshots, and then merged
into [Gen0 files](/influxdb3/enterprise/performance-preview/configure/#gen0).
The upgraded storage layer organizes compacted data into 24-hour UTC windows
and progresses data through four compaction levels (L1 through L4).
and progresses Gen0 files through four [compaction levels (L1 through L4)](/influxdb3/enterprise/performance-preview/configure/#l1-l4-level-tuning).
Compaction runs continuously in the background with a byte-based memory budget
(default: 50% of system RAM), so it never causes resource spikes.

Expand Down
Loading