Hello, as a new user on this subject, I asked this question and gave feedback on this issue. This is definitely not a situation that suits Fedora and we must insist on fixing it. Fedora is actually a distribution that has enough infrastructure to even create its own store; we should demand these.
From your description, I presume you’re using GNOME Software for managing upgrades.
Given that you’re on an atomic version of Fedora, it means that with each update of the system, if available, the latest version of the current tree is being downloaded. Then some other processes, such as performing the deployment of the current tree are involved, which might explain why it seems that an upgrade takes longer than, say, running an upgrade on traditional systems.
I have just performed an upgrade (via command line) on a Silverblue machine, and the average download speed reported was about 4MB/s, which is probably a decent speed provided by some local mirror.
So, in order for you to check if the issue is just a network or mirror speed limitation, or rather if it has to do with GNOME Software, you might want to run the next upgrade from the command line (via rpm-ostree upgrade), and compare it with the time it takes to perform a similar upgrade via GNOME Software. Have a look also at the detailed information you’re receiving from the rpm-ostree upgrade command, and try to associate it with the specific stages of updates via GNOME Software.
It has to be mentioned that an update via GNOME Software doesn’t only perform the update of the OSTree, but also the update of GUI apps (and their runtimes) installed as Flatpaks (which, again, are bigger in size than traditional RPM packages).
I think the gui is slow since it checks flatpaks and rpm-ostree updates and since running rpm-ostree update from terminal it runs only rpm-ostree checks not flatpaks
The GUI is made to get all updates in single click and usually work on background