Skip to content

docs(erasure-coding): replace per-scheme sections with overview table#170

Open
schmidt-scaled wants to merge 2 commits into
mainfrom
docs-ec-scheme-overview-table
Open

docs(erasure-coding): replace per-scheme sections with overview table#170
schmidt-scaled wants to merge 2 commits into
mainfrom
docs-ec-scheme-overview-table

Conversation

@schmidt-scaled

Copy link
Copy Markdown
Contributor

What

On the Erasure Coding Scheme page, replace the seven separate ### Scheme: sections with a single overview table and add the missing 1+0 schema.

Table columns

Schema · tolerated node failures · data protection overhead · IOPS r/w performance & latency · minimum nodes.

Schema Tolerated node failures Overhead IOPS r/w Min. nodes
1+0 0 0% Very good 1
1+1 1 100% Excellent 3
2+1 1 50% Very good 4
4+1 1 25% Very good 6
1+2 2 200% Very good 5
2+2 2 100% Very good 6
4+2 2 50% Very good 8

Notes for review

  • Data protection overhead = additional raw capacity over usable data (parity/mirror cost).
  • Performance ratings per request: excellent for 1+1, very good for the rest. 1+0 is listed as very good to follow that wording — flag if it should be excellent (it has no parity write cost).
  • Added a Tolerated node failures column as it is the defining EC property and distinguishes 1+0.

🤖 Generated with Claude Code

Replace the seven separate '### Scheme:' sections with a single overview
table (schema, tolerated node failures, data protection overhead, IOPS
r/w performance & latency, minimum nodes), and add the missing 1+0
schema. Minimum-node counts: 1+0=1, 1+1=3, 2+1=4, 4+1=6, 1+2=5, 2+2=6,
4+2=8.
@github-actions

Copy link
Copy Markdown
Contributor

🤖: Deployment available as https://docstest.simplyblock.io/docs-ec-scheme-overview-table

FTT (failures to tolerate) is the established term; same values
(0 for 1+0, 1 for n+1, 2 for n+2).
@github-actions

Copy link
Copy Markdown
Contributor

🤖: Deployment available as https://docstest.simplyblock.io/docs-ec-scheme-overview-table

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.

2 participants