Curious about Eopkg

xjdwc

This one is more me being curious. I've always upgraded through the terminal ever since I started using Solus.

One thing that I've noticed in recent times, after 4.3 anyway, is that the norm (4.3 ISO and earlier). That when downloading through the terminal, packages would download and once one is finished it would move to the next package basically instantly. This used to be the norm the whole time I've been using Solus. Now it seems it delays intentionally regardless of your internet speed. Like it's buffering. Just curious as to why.

If you test it for your self on the 4.3 ISO in the terminal then do it with your current system. You can see that there is a noticeable difference.

Seems that the delay between each package would add up to quite a bit of time if the 4.3 ISO was upgrading next to a current system. I haven't tested it, that's just going of pure observation.

Maybe there is a valid reason. Just seems like a backwards step if it takes longer. Maybe it doesn't. Has anyone else noticed this?

In the end its not a deal breaker and can be ignored, just something that I've noticed and am curious about.

tomscharbach

xjdwc [W]hen downloading through the terminal, packages would download and once one is finished it would move to the next package basically instantly. This used to be the norm the whole time I've been using Solus. Now it seems it delays intentionally regardless of your internet speed. Like it's buffering. Just curious as to why.

I usually update through the terminal but I sometimes update through the Software Center. I don't know if there is an actual difference/delay in how the packages are downloaded between the two, but to my mind the Software Center seems a bit slower.

I have noticed using the terminal that I have different download speeds between files. The per-second download speed for small files is reported as higher than the per-second download speed for large files like Firefox, the kernel, and theme-related files (papirus-icon-theme in my case) -- the Mps rate reported by the terminal drops when downloading the largest files. To my mind, that suggests buffering at the RIT mirror, but it could also be something going on with my wifi adapter (which is n-based) or my router. I don't know, but the difference in download rate between small and large files has been consistent over several years.

I would expect that what I am seeing in the terminal is reflected in downloading updates through the Software Center. But I don't know because when I am using the Software Center, I can't dig down below the GUI line, which is not informative because many files do not report download speed for whatever reason.

That's why I wonder whether the perceived difference between terminal and Software Center download behaviors is actual or whether the perceived difference is a function of how the GUI line reports download speeds and sequence. The GUI line gives me basically nothing to look at, while the terminal gives me all sorts of information I don't need.

For what it is worth, though, I haven't noticed a delay between downloads in either the terminal or the Software Center. I did today's update in the Software Center this morning and watched the entire, excruciating process, looking for any delays between downloads. I didn't see anything, but the Software Center GUI is not particularly informative.

Harvey

Haven't noticed but then again I don't sit and watch the terminal while it updates. If I were to guess any slow down would be the result of the changes made to eopkg which allowed it to handle timeouts correctly.

synth-ruiner

I just updated and it was all quick apart from an icon theme package... images are large, as it turns out!

Staudey

synth-ruiner Yeah the icon theme updates (especially the chonky papirus) will always take a while. Just usually include a lot of operations.

I've personally noticed some slowdown for certain eopkg operations (like info), but haven't really investigated further yet. What's expected to be a bit slower is installing a package when there are updates available (but only the initial check before the start) due to Joey's great work on pulling in updates for all affected packages to avoid systems breaking when they haven't been updated in a long while. Building on this there were some additional, necessary refinements to the process though (see e.g. here), so maybe some of that created a bit of a slowdown. That should only apply when there are file conflicts though.