Closed msimonin closed 6 years ago
idea :
# conf.yaml
incremental:
test_case_1:
dynamics:
nbr_clients: [500, 500, 1000, 1000, 1000]
nbr_servers: [5, 5, 10, 10, 10, 10]
pause: [0.1, 0.1, 0.2, 0.3, 0.4, 0.5]
statics:
timeout: 3600
nbr_calls: 1000
1) we compute the dot product of the dynamics parameters (parameters) 2) for params in parameters, we merge params with the statics parameters 2) for params in parameters we call test_case_X_inc that will now how to handle the launch of the test_case (incremental start may differ from one test_case to another).
a new option will be created for campaign
: --incremental
. This option will be set keeping the current configuration of the conf.yaml
file. The logics for the test cases are:
test_case_1
performs a zip
-like operation between nbr_clients
, nbr_servers
, and pause
test_case_2
deploys topics on demandIn both cases the difference of the current agents and total (required) agents are calculated at runtime
👍
Our current workflow is:
In order to scale fast we probably wants to avoid destroying everything between two rounds. I propose to start thinking/writing a campaign-like script that allows to incrementally scale a test_case.