cwinfo/yggdrasil-network.github.io
5
0
Fork 0
mirror of https://github.com/cwinfo/yggdrasil-network.github.io.git synced 2024-09-19 21:52:31 +00:00
Code Releases Activity

Update 2021-06-26-v0-4-prerelease-benchmarks.md

Browse Source
This commit is contained in:
Arceliar 2021-06-26 16:09:10 -05:00 committed by GitHub
parent 0490f2f5cb
commit f85a1d9a5b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_posts/2021-06-26-v0-4-prerelease-benchmarks.md
View File

@ -51,7 +51,7 @@ The `mobility2` test is essentially a much more aggressive variation of the abov
![mobility2_arrival_progress](/assets/images/2021-06-26/mobility2_arrival_progress.svg) ![mobility2_arrival_progress](/assets/images/2021-06-26/mobility2_arrival_progress.svg)
![mobility2_traffic_progress](/assets/images/2021-06-26/mobility2_traffic_progress.svg) ![mobility2_traffic_progress](/assets/images/2021-06-26/mobility2_traffic_progress.svg)
The main feature to note is that, aside from having terrible reliability in this test, `v0.3.16` uses a ridiculous amount of bandwidth when mobility is involved. With `v0.4rc3`, the bandwith use drops to at or below around 10KBps, depending on how mobile things are. I'm fairly certain that most of this bandwith is still a reaction to mobility events in the network, because (as we're about to see) the bandwith use a pretty low in static networks. The main feature to note is that, aside from having terrible reliability in this test, `v0.3.16` uses a ridiculous amount of bandwidth when mobility is involved. With `v0.4rc3`, the bandwith use drops to at or below around 10KBps, depending on how mobile things are. I'm fairly certain that most of this bandwith is still a reaction to mobility events in the network, because (as we're about to see) the bandwith use is pretty low in static networks.
#### Scalability1 #### Scalability1