[Battlemesh] Result documentation RFC

[Henning Rogge]

Hi,

as I said when you contacted me I like the work you did for the graphs...

oh, I also uploaded my whole "battlemesh" folder to Google Drive... it
contains my measurement scripts, the configuration of all 10 mesh nodes and
the results of all tests.

https://drive.google.com/file/d/0B73bEek-LDc5MWZRZGprZXhwc2s/view?usp=sharing

it is ~ 1.5 MByte

Henning

On Fri, Aug 21, 2015 at 8:24 PM, Benjamin Henrion <zoobab at gmail.com> wrote:

> 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?
>
> From what I have heard in the videos, none of the routing protocols
> resists network saturation.
>
> Maybe adding a QOS rule for packets belonging to routing protocols would
> help?
>
> --
> Benjamin Henrion <bhenrion at ffii.org>
> FFII Brussels - +32-484-566109 - +32-2-4148403
> "In July 2005, after several failed attempts to legalise software
> patents in Europe, the patent establishment changed its strategy.
> Instead of explicitly seeking to sanction the patentability of
> software, they are now seeking to create a central European patent
> court, which would establish and enforce patentability rules in their
> favor, without any possibility of correction by competing courts or
> democratically elected legislators."
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20150821/ab65ff7f/attachment.htm>