Far-away transit backhaul is slow, and slow is bad service
Each transit flow's backhaul round trip over your own links (2× the path latency to the exit) now affects service: free up to 20 ms (~1,500 km), up to 20% worse at 50 ms, and half the service value past 50 ms. sfOf() multiplies delivery by it, so revenue, broadband growth and business customers all feel it. Peering, PNIs and caches are exempt. City panel chip and Transit-tab warning name the far exit and the round trip; the NOC lists slow cities. Two tests updated: Moscow on Frankfurt transit is still fully delivered but now slow, and the Red Sea test pins Asian demand that would otherwise churn away on Marseille transit.
This commit is contained in:
parent
4643adb2ea
commit
68b3d0b839
9 changed files with 111 additions and 14 deletions
|
|
@ -10,7 +10,7 @@
|
|||
"url": "git+https://github.com/fjaeckel/seriesoftubes.git"
|
||||
},
|
||||
"scripts": {
|
||||
"test": "node --test --test-concurrency=1 tests/game.test.js tests/build.test.js tests/persist.test.js tests/services.test.js tests/peering.test.js tests/inbox.test.js tests/issues.test.js tests/regions.test.js tests/modes.test.js tests/levels.test.js tests/speed.test.js tests/i18n.test.js tests/routing-reference.test.js tests/perf.test.js tests/sea-routing.test.js",
|
||||
"test": "node --test --test-concurrency=1 tests/game.test.js tests/build.test.js tests/persist.test.js tests/services.test.js tests/peering.test.js tests/inbox.test.js tests/latency.test.js tests/issues.test.js tests/regions.test.js tests/modes.test.js tests/levels.test.js tests/speed.test.js tests/i18n.test.js tests/routing-reference.test.js tests/perf.test.js tests/sea-routing.test.js",
|
||||
"build": "bash scripts/build.sh",
|
||||
"i18n:check": "node scripts/i18n-check.js",
|
||||
"serve": "npm run build && npx --yes serve@14.2.4 _site",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue