Skip to content

Conversation

@jstirnaman
Copy link
Collaborator

@jstirnaman jstirnaman commented Jan 2, 2026

Summary

Add performance considerations section to the Downsampler plugin documentation, addressing DAR#558.

Changes

  • Added "Consolidate calculations in fewer triggers" guidance
  • Added recommended vs not-recommended patterns with styled headings
  • Added specific_fields best practice documentation
  • Reorganized performance tips into subsections

Key Finding

Internal testing showed:

  • 134 individual triggers (one calculation each) → degraded cluster performance, high CPU/memory
  • Consolidated triggers (all calculations per measurement) → ~4% CPU, stable memory

Test Plan

  • Verify README renders correctly on GitHub

Deploy Plan

The workflow is:

  1. Merge feat(sync): extract style attributes from HTML comments docs-v2#6694 first (style extraction support)
  2. Merge docs(downsampler): add performance considerations for trigger design #37 - this should trigger the sync workflow
  3. Merge docs: add CLAUDE.md files for generated content directories docs-v2#6690 (CLAUDE.md files)

Add guidance on consolidating calculations in fewer triggers for better
cluster performance. Internal testing showed that 134 individual triggers
caused high CPU/memory usage, while consolidated triggers (all calculations
per measurement) reduced CPU to ~4% with stable memory.

Includes:
- Recommended pattern with single trigger per measurement
- Not recommended pattern showing anti-pattern to avoid
- specific_fields guidance to limit processing
- Additional performance tips

closes influxdata/DAR#558
@jstirnaman jstirnaman force-pushed the dar-558-downsampler-performance branch from 9656083 to cfe38a3 Compare January 2, 2026 22:46
- **Many triggers** (one calculation each): When 134 triggers were created, each handling a single calculation for a measurement, the cluster showed degraded performance with high CPU and memory usage.
- **Consolidated triggers** (all calculations per measurement): When triggers were restructured so each one performed all necessary field calculations for a measurement, CPU usage dropped to approximately 4% and memory remained stable.

#### Recommended <!-- {.green} -->
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jstirnaman Rename style to .recommended after support is added in influxdata/docs-v2

temperature_hourly_downsample
```

#### Not recommended <!-- {.orange} -->
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jstirnaman Rename style to .not-recommended after support is added in influxdata/docs-v2

@jstirnaman jstirnaman merged commit 2e0f906 into main Jan 5, 2026
@jstirnaman jstirnaman deleted the dar-558-downsampler-performance branch January 5, 2026 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants