The only thing this list of processes shows is that Anaconda devs did a good job in the last years on making the backend more modular, and systemd does good job in visualizing it.
So yes, instead of one process called “anaconda” you see components which are involved in the installation process. These components are not new, the fact that you see them listed as modules is new.
The main resource requirements on the installation process do not come from Anaconda. they come from two places:
-
The package installation which Anaconda needs to trigger. Package manager needs quite a lot of resources especially when it deals with large list of packages for the initial installation and not just a couple of updates as in regular post-install workflows.
-
Graphical environment. WebUI or GTK UI - there is no big difference here, it is the need to show the UI locally on the system which bumps the resource requirements as we need to run a whole desktop to be able to show a UI at all. We try to reduce this dependency by using GNOME Kiosk instead of full GNOME Shell, but it is still quite a lot.
Remote installation solves that second part. Unlike RDP and VNC approach to remote installation, which adds couple of layers of complexity on top of the full local installation environment, installation over web removes the unnecessary layers, the need to deal with things like passing complex shortcuts to the remote desktop, copy-paste, keyboard layout switch.., and makes the whole process simple.