StefanLobbenmeierObjego
commented
1 month ago I am currently checking the nx source code for this:
The worker is created here:
function createWorkerPool(numberOfWorkers) {
const res = [];
for (let i = 0; i < numberOfWorkers; ++i) {
res.push(new (require('worker_threads').Worker)((0, path_1.join)(__dirname, './project-graph-worker.js'), {
env: process.env,
}));
}
return res;
}Looking up the stack we see this:
function buildExplicitDependenciesUsingWorkers(jsPluginConfig, ctx, totalNumOfFilesToProcess, builder) {
const numberOfWorkers = Math.min(totalNumOfFilesToProcess, getNumberOfWorkers());
const bins = splitFilesIntoBins(ctx, totalNumOfFilesToProcess, numberOfWorkers);
const workers = createWorkerPool(numberOfWorkers);
let numberOfExpectedResponses = bins.length;
// ...function buildExplicitDependencies(jsPluginConfig, ctx, builder) {
let totalNumOfFilesToProcess = totalNumberOfFilesToProcess(ctx);
// using workers has an overhead, so we only do it when the number of
// files we need to process is >= 100 and there are more than 2 CPUs
// to be able to use at least 2 workers (1 worker per CPU and
// 1 CPU for the main thread)
if (totalNumOfFilesToProcess < 100 || getNumberOfWorkers() <= 2) {
return buildExplicitDependenciesWithoutWorkers(jsPluginConfig, ctx, builder);
}
else {
return buildExplicitDependenciesUsingWorkers(jsPluginConfig, ctx, totalNumOfFilesToProcess, builder);
}
}it seems when there are 2 or less threads, nx does not use workers, so it never runs into that path.
ronnetzer
I'm submitting a...
Current behavior
When starting on ubuntu-latest-4-cores, the nx-distributed-task step fails with this error:
Cannot find module '/home/runner/work/_actions/e-square-io/nx-distributed-task/v2/project-graph-worker.js'
Expected behavior
No error, just like on ubuntu-latest
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
The nx project I use has one big project and many small ones. I would like to run the big project on a bigger runner to speed up CI. So I use 4 cores for that one, but unfortunately this seems to be incompatible with this project
Environment
Logs