[Question] performance between flat npm-run-all -p vs nested npm-run-all -p

mysticatea / npm-run-all

A CLI tool to run multiple npm-scripts in parallel or sequential.

MIT License

5.72k stars 240 forks source link

[Question] performance between flat npm-run-all -p vs nested npm-run-all -p #160

Open dereklin opened 5 years ago

dereklin commented 5 years ago

I was wondering if there were any comparison done for performance between flat npm-run-all -p vs nested npm-run-all -p.

Let's say I have 100 tasks/commands.

I can do npm-run-all -p all-100-tasks...

or I can group the 100 tasks into 10 groups/scripts with each one running npm-run-all -p 10-tasks... and then run

npm-run-all -p the-10-grouped-scripts...

Is there any difference in terms of performance?

How about when 100 tasks becomes 1,000 or 10,000 tasks?

mysticatea commented 5 years ago

Thank you for this issue.

I have not tried such a many tasks. In general, npm-run-all spawns npm run-script xxx process and the spawned npm run-script xxx process spawns a sh process with the script body of xxx. That means there are 3 processes at least for each task. I don't think if that has good performance.