For the moment, a participant measures ping time for all of the perfMessage it sends. So it may happen that the first PerfMessage messages or the last one experience different ping times, because not all of the participants are broadcasting at the same time.
To solution this problem, a program argument should be added to specify a warmup/cooldown phase:
Warmup phase starts at the beginning of the experiment: Ping time of PerfMessage sent during this phase are not memorized for statistics.
Cooldown phase takes place at the end of the experiment: Ping time of PerfMessage sent during this phase are not memorized for statistics.
Argument (specified by -w|--warmupCooldown) is a number between 0 and 49. It represents the percentage of total number of PerfMessage sent which should be considered as part of warmup phase. The same percentage is applied for messages of cooldown phase.
Example: If argument is 5, 5% of PerfMessage messages will be considered as part of warmup phase, and another 5% will be considered as part of cooldown phase.
For the moment, a participant measures ping time for all of the perfMessage it sends. So it may happen that the first PerfMessage messages or the last one experience different ping times, because not all of the participants are broadcasting at the same time.
To solution this problem, a program argument should be added to specify a warmup/cooldown phase:
Argument (specified by -w|--warmupCooldown) is a number between 0 and 49. It represents the percentage of total number of PerfMessage sent which should be considered as part of warmup phase. The same percentage is applied for messages of cooldown phase.
Example: If argument is 5, 5% of PerfMessage messages will be considered as part of warmup phase, and another 5% will be considered as part of cooldown phase.