summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorbnewbold <bnewbold@robocracy.org>2012-06-05 21:05:57 -0400
committerbnewbold <bnewbold@robocracy.org>2012-06-05 21:05:57 -0400
commit933ed9a711197da23f7996d6e85678e32f24c64b (patch)
tree29574fe28a842cf43bddaf39b66111cd11cc4d65
parent3bdbdd684795f1910f7420675830f8d1b12cd97b (diff)
downloadknowledge-933ed9a711197da23f7996d6e85678e32f24c64b.tar.gz
knowledge-933ed9a711197da23f7996d6e85678e32f24c64b.zip
bandwidth notes
-rw-r--r--networking/bandwidth.page13
1 files changed, 13 insertions, 0 deletions
diff --git a/networking/bandwidth.page b/networking/bandwidth.page
new file mode 100644
index 0000000..faddc29
--- /dev/null
+++ b/networking/bandwidth.page
@@ -0,0 +1,13 @@
+
+Throughput data/day data/month data/year
+--------------- ------------ ------------ ------------
+128 Kbit/sec 1.4 GByte 41.5 GByte 505.6 GByte
+1 Mbit/sec 10.8 GByte 324 GByte 3.8 TByte
+20 Mbit/sec 100.8 GByte 6.48 TByte 78.8 TByte
+1 Gbit/sec 10.8 TByte 324 TByte 3.94 PByte
+
+200 GByte a month is about 610 Kbit/sec ("kbps") continuous.
+
+Networks must be provisioned for "peak use" periods, which likely correlate for
+users in the same region, so enforcing or charging for total throughput doesn't
+seem to make much sense?