Skip to content

RDBMS: benchmark results#8159

Open
christinaausley wants to merge 1 commit intomainfrom
benchmarking-rdbms
Open

RDBMS: benchmark results#8159
christinaausley wants to merge 1 commit intomainfrom
benchmarking-rdbms

Conversation

@christinaausley
Copy link
Contributor

Description

Closes #8004. Adds external, user-facing RDBMS benchmark results documentation.

Changes

  • Added docs/self-managed/concepts/secondary-storage/rdbms-benchmark-results.md
  • Linked from docs/self-managed/concepts/secondary-storage/index.md
  • Linked from docs/self-managed/concepts/databases/overview.md
  • Linked from docs/components/best-practices/architecture/sizing-your-environment.md

Decisions (and why)

  • Placement for now: Under secondary storage concepts, since this content is primarily architecture/trade-off guidance.
  • Sizing cross-link: Included so benchmark outcomes are discoverable from capacity-planning flow.
  • PostgreSQL-first: Scoped to validated benchmark coverage.
  • Framing: Use relative/qualitative guidance with explicit caveats...avoid brittle hard guarantees.

Out of scope

  • Automated benchmark publishing pipeline.
  • Full IA move to a dedicated Best Practices benchmarking section.

When should this change go live?

  • This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
  • This is already available but undocumented and should be released within a week. (add available & undocumented label)
  • This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
  • This is part of a scheduled alpha or minor. (add alpha or minor label)
  • There is no urgency with this change (add low prio label)

PR Checklist

  • My changes are for an upcoming minor release and are in the /docs directory (version 8.9).
  • My changes are for an already released minor and are in a /versioned_docs directory.

@christinaausley christinaausley self-assigned this Mar 5, 2026
@christinaausley christinaausley added severity/mid Marks a bug as having a noticeable impact but with a known workaround rdbms labels Mar 5, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2026

👋 🤖 🤔 Hello, @christinaausley! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.8/.

  • docs/components/best-practices/architecture/sizing-your-environment.md
  • docs/self-managed/concepts/databases/overview.md
  • docs/self-managed/concepts/secondary-storage/index.md
  • docs/self-managed/concepts/secondary-storage/rdbms-benchmark-results.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rdbms severity/mid Marks a bug as having a noticeable impact but with a known workaround

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Define and document RDBMS/secondary storage benchmarking strategy

1 participant