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

Workers should be divided by spec, not fuzzing target #84

Open
jschwartzentruber opened this issue Jan 25, 2021 · 1 comment
Open

Workers should be divided by spec, not fuzzing target #84

jschwartzentruber opened this issue Jan 25, 2021 · 1 comment

Comments

@jschwartzentruber
Copy link
Contributor

Currently we allocate a TC worker-pool per fuzzing pool. We should instead define pools based on specs (machine types allowed, worker features/capabilities required), which can be used by one or more fuzzing pool. The max pool size would scale based on the sum of fuzzing pools using it.

This would allow us to modify machine specs without worrying about "stale" workers using an older configuration.

@jschwartzentruber
Copy link
Contributor Author

Implementing this would also simplify scheduling on physical machines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant