A benchmarking test is implemented for Cyclone that processes a complete communication cycle
between the master and controller with given number of worker.
It can also be considered as an scalability test for the application,
how many messages can be processed for a given time period.
A benchmark task does simulate a very small load by doing a sleep between 0 to 100ms.
To drop the wait time and get a more precise result for the message communication this issue should be considered.
The benchmarking can also be used for testing the communication protocoll within Cyclone.
Example config file for the task generator
| Name | Type | Value | Description |
|---|---|---|---|
| num_tasks | int | 1-100M | Number of tasks to be processed |
| poll_time_ms | int | 1-1000 | Time for the task generator to check for finished tasks |