docs(traffic-shaping): Correct monthly transfer estimates#282
Merged
Conversation
The "Examples of traffic limits" section mapped each bandwidth cap to a monthly volume using TiB/month = Mbit/s / 100, which has no physical basis (the values were low by roughly 30x). Recalculate using sustained-transfer math (~0.3 TiB/month per Mbit/s over an average 730-hour month) and add the formula inline so the numbers are reproducible. Values are framed as "up to" to reflect that they are ceilings assuming the cap is saturated continuously.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
Scan for commit: 🔒 Security Scan ResultsScanned files: 1 ✅ No security issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "Examples of traffic limits" section mapped each bandwidth cap to a monthly volume using TiB/month = Mbit/s / 100, which has no physical basis (the values were low by roughly 30x).
Recalculate using sustained-transfer math (~0.3 TiB/month per Mbit/s over an average 730-hour month) and add the formula inline so the numbers are reproducible. Values are framed as "up to" to reflect that they are ceilings assuming the cap is saturated continuously.
What does this PR do?
🛑 Please open an issue first to discuss any significant work and flesh out details/direction — we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.
Motivation
Type of Change
Testing
npm run buildsuccessfullynpm run testand all tests passnpx cdk synthwith a sample.env(e.g. fromblueprints/dummy/samples/) and it succeedsnpm run run-pre-commitNew Blueprint Checklist (if adding a protocol)
blueprints/dummy/(reference implementation).envfiles are provided for at least one network (mainnet or testnet)blueprints/dummy/)website/docs/blueprints/(.mdx mirror importing README)Documentation
cd website && npm run buildwith no broken links (if docs changed)License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.