Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document ideas for doing spike tests #297

Open
damies13 opened this issue Sep 17, 2024 · 1 comment
Open

Document ideas for doing spike tests #297

damies13 opened this issue Sep 17, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@damies13
Copy link
Owner

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

@damies13 damies13 added the enhancement New feature or request label Sep 17, 2024
@damies13
Copy link
Owner Author

Added Syncronise On Timestamp keyword to perftest.resource

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant