Due to internal limitations, it is not able to be scaled up, which is a big problem for robustness of the oSparc platform.
### Tasks
- [ ] computational scheduler: remove in process data and rely only on database before scheduling pipelines
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/5631
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/5632
restart phase: there are 2 instances running in parallel for some time (even small), which means it needs to be scalable first or unintended stuff might happen
I think what you want is a kind of stateless service (which is also what I want), and that it can restart while osparc is running. But while we have several instances up they need to play nice with each other, then you can restart 1 instance without breaking computation pipelines or running dynamic services.
Currently the dv-2 has 2 main jobs:
Due to internal limitations, it is not able to be scaled up, which is a big problem for robustness of the oSparc platform.