mirror of
https://github.com/LibreQoE/LibreQoS.git
synced 2026-10-25 14:20:05 -05:00
Merge pull request #369 from LibreQoE/main
Bring long_term_stats up to date with main
This commit is contained in:
2 files changed
+7
-4
No files matched your search
@@ -69,10 +69,12 @@ Single-thread CPU performance will determine the max throughput of a single HTB
|
||||
| Customer Max Plan | Passmark Single-Thread |
|
||||
| --------------------| ------------------------ |
|
||||
| 100 Mbps | 1000 |
|
||||
| 250 Mbps | 1500 |
|
||||
| 500 Mbps | 2000 |
|
||||
| 1 Gbps | 2500 |
|
||||
| 2 Gbps | 3000 |
|
||||
| 250 Mbps | 1250 |
|
||||
| 500 Mbps | 1500 |
|
||||
| 1 Gbps | 1750 |
|
||||
| 2 Gbps | 2000 |
|
||||
| 3 Gbps | 2500 |
|
||||
| 4 Gbps | 3000 |
|
||||
|
||||
Below is a table of approximate aggregate throughput capacity, assuming a a CPU with a [single thread](https://www.cpubenchmark.net/singleThread.html#server-thread) performance of 2700 or greater:
|
||||
|
||||
|
||||
@@ -17,6 +17,7 @@ upstreamBandwidthCapacityUploadMbps = 1000
|
||||
# Devices in ShapedDevices.csv without a defined ParentNode (such as if you have a flat {} network)
|
||||
# will be placed under one of these generated parent node, evenly spread out across CPU cores.
|
||||
# This defines the bandwidth limit for each of those generated parent nodes.
|
||||
# If you are not sure what values to use, simply use the same values as upstreamBandwidthCapacityDownloadMbps and upstreamBandwidthCapacityUploadMbps
|
||||
generatedPNDownloadMbps = 1000
|
||||
generatedPNUploadMbps = 1000
|
||||
|
||||
|
||||
Reference in new issue
Block a user