Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • LinkTest LinkTest
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • cstao-public
  • LinkTestLinkTest
  • Wiki
  • Noteworthy Reports

Noteworthy Reports · Changes

Page history
Update to Noteworthy Reports to include unidirectional reports with correct titles. authored Oct 10, 2021 by Max Holicki's avatar Max Holicki
Hide whitespace changes
Inline Side-by-side
Noteworthy-Reports.md
View page @ cc5becfe
......@@ -59,9 +59,9 @@ Bidirectional testing is a different type of test entirely. Uni- and semi-direct
What this means for bidirectional testing is that it should be used only when bidirectional communication is expected to cause communication congestion that will cause both messages to be transferred slower, or to test if this is the case. Bidirectional testing cannot pick up on network-topology anisotropy between nodes, it can, however, measure congestion effects when trying to communicate in both directions at the same time.
Let us now illustrate this with an example. We have a network with two nodes `Mew` and `Mewtwo` and an auxiliary node, the `Pokémon Center`. We now conduct uni-, semi- and bi-directional tests between the nodes and find that the results between the nodes for all three tests are very similar. Here are the [reports](uploads/fbc5f106e7eb4795494d0625a26fae5b/Pokemon.pdf).
Let us now illustrate this with an example. We have a network with two nodes `Mew` and `Mewtwo` and an auxiliary node, the `Pokémon Center`. We now conduct uni-, semi- and bi-directional tests between the nodes and find that the results between the nodes for all three tests are very similar. Here are the [reports](uploads/49568fb564022dc0b6e1244da4616bc1/Pokemon.pdf).
Now `Mewtwo` catches `Pokérus`, which causes it to have to send messages with a size greater than 1 kiB via `Bill's PC`, which is only reachable via the `Pokémon Center`. All of a sudden messages from `Mewtwo` to `Mew` take twice as long to arrive. This effect can be measured. Redoing the three tests we find very different results. Here are the [reports](uploads/cd3978040b6e87e9d7b4370a65e5c2de/Pokemon_Pokerus.pdf).
Now `Mewtwo` catches `Pokérus`, which causes it to have to send messages with a size greater than 1 kiB via `Bill's PC`, which is only reachable via the `Pokémon Center`. All of a sudden messages from `Mewtwo` to `Mew` take twice as long to arrive. This effect can be measured. Redoing the three tests we find very different results. Here are the [reports](uploads/2a8164691c9ceeebb20946770640bf94/Pokemon_Pokerus.pdf).
The changes make sense when we think of the discussion above. The network topology is now anisotropic between `Mew` and `Mewtwo`, which causes the unidirectional connection between `Mewtwo` and `Mew` to be slower. This has knock-on effects to the semi- and bi-directional tests causing the measured times to be larger.
......
Clone repository
  • Acknowledgements
  • Build
  • Communication Patterns
  • Frequently Asked Questions
  • Glossary
  • Inspecting LinkTest SION Files with ImHex
  • LinkTest Python Reader
  • LinkTest Report
  • LinkTest SIONlib File Format
  • LinkTest
  • Noteworthy Reports
  • Old LinkTest SIONlib File Formats
  • Old Stable LinkTest Releases (<2.0.0)
  • Semi‐, Bi‐ & Uni‐directional Testing
  • Troubleshooting
View All Pages