Skip to content

docs: add Volume Sizing Guidance - #1311

Open
sushant-suse wants to merge 1 commit into
longhorn:masterfrom
sushant-suse:issue#12203-add-volume-sizing-guidance
Open

docs: add Volume Sizing Guidance#1311
sushant-suse wants to merge 1 commit into
longhorn:masterfrom
sushant-suse:issue#12203-add-volume-sizing-guidance

Conversation

@sushant-suse

Copy link
Copy Markdown
Contributor

Which issue(s) this PR fixes:

Related Issue

What this PR does / why we need it:

This PR adds volume sizing guidance. It addresses the need for users to understand the maximum recommended volume size based on "Time-to-Recovery" constraints rather than just storage capacity. It provides a structured formula to calculate sizing based on network/disk bottlenecks and the default 24-hour rebuild timeout, ensuring cluster stability during replica rebuilding.

Special notes for your reviewer:

  • The primary technical content is added to volume-size.md to keep it contextually relevant to existing "Actual vs. Nominal" size explanations.
  • A cross-reference is also added to the best-practices.md page under "Volumes Performance Optimization".
  • The math and case studies are derived from current Longhorn scalability benchmarks and the default concurrent rebuild limit (5).

Additional documentation or context:

N/A

@netlify

netlify Bot commented Feb 3, 2026

Copy link
Copy Markdown

Deploy Preview for longhornio ready!

Name Link
🔨 Latest commit 394ea8c
🔍 Latest deploy log https://app.netlify.com/projects/longhornio/deploys/6a0bfad988b2600008806a46
😎 Deploy Preview https://deploy-preview-1311--longhornio.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@mantissahz
mantissahz requested a review from derekbit February 3, 2026 12:34
Signed-off-by: sushant-suse <sushant.gaurav@suse.com>
@derekbit
derekbit force-pushed the issue#12203-add-volume-sizing-guidance branch from 8ed967c to 394ea8c Compare May 19, 2026 05:53
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.

1 participant