Recent runs actually showed that the loader git:
- uses too much memory
- does too much work (regarding forks, it does not deduplicate computations for in the end noops)
- is too slow to finish which renders maintenance a pain
So in given too much concurrency, it could actually be not that stable.
This task is actually a parent task to track the work done to actually improve those points, make the loader git:
- uses less memory
- do less unneeded work
- stops fast when required to
The perimeter of this task is frozen to this 3 points (it's not a neverending task ;)