Bug 31802 - drakrpm may need a performance boost
Summary: drakrpm may need a performance boost
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-16 19:53 CEST by fadi halim
Modified: 2023-05-13 18:49 CEST (History)
0 users

See Also:
Source RPM: rpmdrake
CVE:
Status comment:


Attachments

Description fadi halim 2023-04-16 19:53:19 CEST
the software installer downloads rpms quickly but takes a slightly long time installing them and a very long time refreshing the packages after the installation . In comparison with synaptic it is noticeably slow . It is not a specific bug in particular , but I hope in the future release the developers may improve its performance .
Comment 1 Lewis Smith 2023-04-16 20:40:10 CEST
This is something very dependent on 'horsepower'. Accepting that rpmdrake is slower than say synaptic on the same box, having recently got a new more powerful machine, package installation and subsequent refresh happens very quickly.

It is unlikely that anything can be done with the software as it is, or that this will ever be signifcantly improved. But I pass your comment on.

Assignee: bugsquad => mageiatools
Source RPM: (none) => rpmdrake
Severity: normal => enhancement

Comment 2 fadi halim 2023-05-13 16:10:34 CEST
I think you should allow an option to disable auto refresh and off course add a button to reload packages . synaptic does not auto refresh and has a reload button. Zypper auto refreshes on startup but has button to disable auto refresh.  rpmdrake auto refresh packages on startup and after each installation and this is what I think slows it down in comparison with the others.
fadi halim 2023-05-13 16:54:54 CEST

Summary: drakrpm may need a performance boost => drakrpm should make package auto refresh optional

Comment 3 sturmvogel 2023-05-13 16:59:07 CEST
As Lewis already wrote, it depends mainly on your hardware specs.

Disabling "refresh" is a really bad idea. This can be seen on many threads in the openSUSE forums where absolute clueless users get in troubles because they disabled "refresh". Having outdated repos causes the most problems...

Can you provide qualified measuring values between the different tools on different distros and implementations? Can you also provide qualified comparisons between the different technical backgrounds and implementations of zypper, yast2-softweare, urpmi, drakrpm, apt, synaptic, ....?

Summary: drakrpm should make package auto refresh optional => drakrpm may need a performance boost

Comment 4 fadi halim 2023-05-13 17:09:08 CEST
At least it should not auto refresh after each installation , only on startup.
Comment 5 fadi halim 2023-05-13 17:12:12 CEST
Plus I am asking for an optional behaviour not a default one .
Comment 6 sturmvogel 2023-05-13 17:22:16 CEST
Please don't confuse different topics and mechanisms.

The "refresh" which you can disable in openSUSE for zypper is ONLY for the repos. Repos only get refreshed once prior start of installation of a package and never after it. This is the same on Mageia.

Users who only use graphical tools like drakrpm, synaptic and yast2-software don't see what happens and can't understand what is going on behind the scenes. You should try the basic tools on terminal to learn what is going on.

If you do a package installation via terminal with zypper, apt or urpmi you will understand and see the the repos only get refreshed before installation.

Everything which happens after installation of a package is a rebuild/actualisation of the (installed) package database or run of post-installation scripts or rebuild of the initrd. This can't be ommitted or your system will break. If you only use graphical tools like synaptic, drakrpm, yast2-software you don't see the run of post-installation scripts, rebuil of initrd and so on....


So maybe the use of basic terminal tools may help you to understand what is going on when you think that graphical tools are "slow".
Comment 7 fadi halim 2023-05-13 18:09:25 CEST
Thanks for clarifying things to me. I take back my request I suspect the culprit is my weak processor :

CPU: Dual Core Celeron T3000 (-MCP-) speed: 1794 MHz Kernel: 5.10.0-22-686-pae i686  
Mem: 1945.5 MiB 

Although I have synaptic on another partition and it feels a little bit faster..Thanks anyway.
Comment 8 fadi halim 2023-05-13 18:49:01 CEST
I am marking the issue as resolved.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.