This was inspired by a conversation on Discord with Jari Uhre (juhrecgi) on the 11th September 2024, 16:50
My reply about Spike testing:
[20:53]damies13:
is there any 'master switch mode' then with what you could turn that kind of 'activate ALL NOW' switch on
Do you mean for spike testing? no there's nothing in RFSwarm for that currently, actually your the first to ask for it, If you want to raise a feature request for this I can try to add a synchronisation point that robot framework can use. I guess you could get all the robots to wait until the time is 00:00 or the timestamp ends with 0000 or something like that
At the moment the manager just hands out jobs gradually to each agent, then the agents poll the manager to find out which jobs have been assigned to them and they run the robot file and test that's part of that job.
In practice I've find you will need a lot more CPU if you ramp up quickly more than 2 robots per cpu core on the agent, so more physical agent machines and more cpu cores per agent will allow after ramp up
This was inspired by a conversation on Discord with Jari Uhre (juhrecgi) on the 11th September 2024, 16:50
My reply about Spike testing:
[20:53]damies13:
Do you mean for spike testing? no there's nothing in RFSwarm for that currently, actually your the first to ask for it, If you want to raise a feature request for this I can try to add a synchronisation point that robot framework can use. I guess you could get all the robots to wait until the time is 00:00 or the timestamp ends with 0000 or something like that
At the moment the manager just hands out jobs gradually to each agent, then the agents poll the manager to find out which jobs have been assigned to them and they run the robot file and test that's part of that job.
In practice I've find you will need a lot more CPU if you ramp up quickly more than 2 robots per cpu core on the agent, so more physical agent machines and more cpu cores per agent will allow after ramp up