Closed OneCDOnly closed 1 year ago
I've been thinking about this one.
The actions start
, install
, reinstall
& upgrade
will cause an issue on older-model NAS if run concurrently, so these shouldn't be (unless a way is included to determine NAS that will handle concurrency without causing massive delays).
Maybe use number of CPU cores as a rough guide? E.g. if CPU has 2 cores, then allow 2 of the aforementioned actions to run at the same time.
e.g. when installing dependents, there's no-need to wait for each one to complete: they can all be installed concurrently.
This will only work on packages in the same tier, and selected for the same operation.