[Battlemesh] Result documentation RFC

Benjamin Henrion zoobab at gmail.com
Fri Aug 21 18:24:01 UTC 2015


On Fri, Aug 21, 2015 at 7:47 PM, Nemesis <nemesis at ninux.org> wrote:
> Hi everybody,
>
> this is a request for feedback: comments, suggestions and pull requests.
>
> See here:
> http://battlemesh-test-docs.readthedocs.org/v8/index.html
>
> Before starting to work on it I exchanged a few ideas via chat with Amadeus
> and Henning.
>
> Here's a quick recap:
>
> having all the results on one page would have made it quite hard to read
> so the tests have been split in 3 pages
>
> mesh of adversity: one single stream from client (connected to A) to server
> (connected to K)
>
> reboot
> ping
> ping + iperf
>
> crossed streams jeopardy: two streams, client A to server K and node D to
> node H
>
> 10 mbit iperf streams
> 100 mbit iperf streams
>
> blowing up the network: tests performed with Flent by Toke
>
> Realtime Response Under Load (RRUL)
> Realtime Response Under Load Best Effort (RRUL_BE)
> 8-stream download test
> TCP upload
> TCP download
>
> As you can see, there are quite a few things that can be improved!
>
> some graphs are missing (some purposely and some I was not able to generate
> properly)
> english needs to be checked
> it would be good to provide some additional explanation to the graphs
> shall we add a conclusion section to each page? if yes, anybody willing to
> propose a conclusion?
> shall we add a last "lessons learned" page with all the things that went
> wrong and the proposed solutions for the next edition?



More information about the Battlemesh mailing list