You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: