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
I had an idea last night: if we ever have recipes that, when run, don't take up all of the cores on a machine, we can bin-pack the recipes such that we run as many of them as possible while making each of them serve as stress for the other.
We currently have the ability to run parallel tests on the runner, but it literally just worker-pools recipes and that usually results in thrashing that slows all of the tests down.
The text was updated successfully, but these errors were encountered:
I had an idea last night: if we ever have recipes that, when run, don't take up all of the cores on a machine, we can bin-pack the recipes such that we run as many of them as possible while making each of them serve as stress for the other.
We currently have the ability to run parallel tests on the runner, but it literally just worker-pools recipes and that usually results in thrashing that slows all of the tests down.
The text was updated successfully, but these errors were encountered: