very slow YaST Software Management on hp 650G2 laptop

English Applications
1

All other programs seem to run fine, at normal speed. Only the YAST takes about a minute or more to initialize. My internet speed is 100 Mbps-download
Any suggestions where to look?

System:
  Kernel: 5.19.2-1-default arch: x86_64 bits: 64 compiler: gcc v: 12.1.1 Console: pty pts/1
    Distro: openSUSE Tumbleweed 20220823
Machine:
  Type: Laptop System: HP product: HP ProBook 650 G2 v: N/A serial: <filter>
  Mobo: HP model: 80FD v: KBC Version 22.74 serial: <filter> UEFI: HP v: N76 Ver. 01.57
    date: 07/28/2022
Drives:
  Local Storage: total: 342.81 GiB used: 12.77 GiB (3.7%)
  ID-1: /dev/sda vendor: Lexar model: 240GB SSD size: 223.57 GiB
  ID-2: /dev/sdb vendor: SanDisk model: SD8SN8U-128G-1006 size: 119.24 GiB
2

I do not think starting YaST needs anything from the network.

3

Are you referring to YaST Control Center or to a specific YaST module, perhaps Software Management as you mention internet speed?

If you are referring to Software Management then be aware a “slow” start may be quite normal if repositories are set to auto-refresh.

4

In which case it is pretty clear what repository is refreshed and thus details about that should be available.

I guess we both think the OP does not tell exact what he experiences. So please @nstst give more details, like: I click on the YaST icon from the main menu and then it takes more then a minute before I see anything happening (like the YaST window appearing). Please be aware that we can not look over your shoulder.

5

YAST>Software Management is the module and this happens even if they were refreshed a minute ago .Also if it is about deletion or installation
I have other computers and that makes me think something is wrong

6

I think reading the installed packages takes the most time

7

I changed the title of the thread. I assume it now better explaining what you want to talk about.

8

Please read again what you wrote and contemplate a bit about what the others here have to understand from it.

Is it slow when starting YaST > Software > Software Managemen (that is until the window is completed)?
Is it slow when you from that module install and.or delete something?
Or is it in both cases?

We can NOT look over your shoulders and depend completely upon your descriptions. So better describe as precise as possible. Where do you click, what is the last change in the window before it stalls for that minute, etc. Every bit of information can lead to someone having an idea about how to investigate further. People here are willing to help, but most are going to do something else when you present them with a vague cloud of possibilities.

BTW when you use zypper to install/remove a package, do you experience the same problem?

9

@nstst

As @hcvv wrote, more detailed information is required before any useful advice or help could be given.

However, in general regarding the initialisation of “(YaST -> Software ->) Software Management”:

Assuming that all enabled repositories are set to “Automatically Refresh” then repositories will be checked to see if they need to be refreshed, if so the repository metadata will be retrieved and the repository cache rebuilt. How long that takes will depend on several factors; such as:

The number of enabled repositories and whether they are mirrored.
Although you have a 100Mbps connection from your ISP to your modem/router that doesn’t mean downloads will be at that speed, there are other limiting factors, some of which are: server capacity/load, overall (wide area) network load, if using wifi to connect to your modem/router then link speed and quality.
For rebuilding the repository cache, processor / hdd / sdd speed are the prime constraints.

I’ve little if any experience of using “(YaST -> Software ->) Software Management” on my Tumbleweed systems, but do use it frequently on my Leap systems.

For comparison, on one of my Leap 15.3 systems (AMD FX-6300 Six-Core Processor + SSD). Although such a comparison is far from valid, as it is akin to comparing apples to potatoes.

“(YaST -> Software ->) Software Management” initialises in approx 47 seconds when all repositories need to be refreshed, and approx 5 seconds when none need refreshing; that is with the “standard” 15.3 repositories plus “packman”, “nvidia”, and “mozilla”.

10

Of course, but one clearly sees that that happens, repository by repository, with progress rulers. So when that is the case, I can not see why the OP not mentions that he sees it, e.g. with every repo, or with one repo, or, …

11

Speed matters. My FTTB connection has 27,5 Mbit/s downstream and 5,5 Mbit/s upstream.

erlangen:~ # time zypper refresh
Repository 'Packman' is up to date.                                                                                   
Repository 'chrome' is up to date.                                                                                    
Repository 'qmapshack (openSUSE_Tumbleweed)' is up to date.                                                           
Repository 'jalbum' is up to date.                                                                                    
Repository 'myrepo' is up to date.                                                                                    
Repository 'Haupt-Repository (NON-OSS)' is up to date.                                                                
Repository 'Haupt-Repository (OSS)' is up to date.                                                                    
Repository 'Hauptaktualisierungs-Repository' is up to date.                                                           
All repositories have been refreshed.

real    0m1.642s
user    0m0.196s
sys     0m0.041s
erlangen:~ #

Cleaning local metadata and reloading:

erlangen:~ # time zypper refresh
Retrieving repository 'Packman' metadata .......................................................................[done]
Building repository 'Packman' cache ............................................................................[done]
Retrieving repository 'chrome' metadata ........................................................................[done]
Building repository 'chrome' cache .............................................................................[done]
Retrieving repository 'qmapshack (openSUSE_Tumbleweed)' metadata ...............................................[done]
Building repository 'qmapshack (openSUSE_Tumbleweed)' cache ....................................................[done]
Retrieving repository 'jalbum' metadata ........................................................................[done]
Building repository 'jalbum' cache .............................................................................[done]
Retrieving repository 'myrepo' metadata ........................................................................[done]
Building repository 'myrepo' cache .............................................................................[done]
Retrieving repository 'Haupt-Repository (NON-OSS)' metadata ....................................................[done]
Building repository 'Haupt-Repository (NON-OSS)' cache .........................................................[done]
Retrieving repository 'Haupt-Repository (OSS)' metadata ........................................................[done]
Building repository 'Haupt-Repository (OSS)' cache .............................................................[done]
Retrieving repository 'Hauptaktualisierungs-Repository' metadata ...............................................[done]
Building repository 'Hauptaktualisierungs-Repository' cache ....................................................[done]
All repositories have been refreshed.

real    0m22.311s
user    0m3.804s
sys     0m0.524s
erlangen:~ # 

erlangen:~ # inxi -zSMCD
System:
  Kernel: 5.18.12-1-default arch: x86_64 bits: 64 Console: pty pts/3
    Distro: openSUSE Tumbleweed 20220824
Machine:
  Type: Desktop Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0
    serial: <filter> UEFI: American Megatrends LLC. v: A.90 date: 03/17/2022
CPU:
  Info: 6-core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP cache:
    L2: 3 MiB
  Speed (MHz): avg: 2250 min/max: 2200/3700 cores: 1: 2200 2: 2200 3: 2200
    4: 2200 5: 2200 6: 2200 7: 2200 8: 2200 9: 2800 10: 2200 11: 2200 12: 2200
Drives:
  Local Storage: total: 3.64 TiB used: 1.77 TiB (48.7%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 2TB
    size: 1.82 TiB
  ID-2: /dev/sdc vendor: Crucial model: CT2000BX500SSD1 size: 1.82 TiB
erlangen:~ #

The notebook is fast too:

notebook:~ # time zypper refresh 
Retrieving repository 'openSUSE-Tumbleweed-Non-Oss' metadata ...................................................[done] 
Building repository 'openSUSE-Tumbleweed-Non-Oss' cache ........................................................[done] 
Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata .......................................................[done] 
Building repository 'openSUSE-Tumbleweed-Oss' cache ............................................................[done] 
Retrieving repository 'openSUSE-Tumbleweed-Update' metadata ....................................................[done] 
Building repository 'openSUSE-Tumbleweed-Update' cache .........................................................[done] 
All repositories have been refreshed. 

real    0m20.460s 
user    0m4.417s 
sys     0m1.465s 
notebook:~ # 

notebook:~ #  inxi -zSMCD
System:
  Kernel: 5.19.2-1-default arch: x86_64 bits: 64 Console: pty pts/3 Distro: openSUSE Tumbleweed
    20220823
Machine:
  Type: Laptop System: LENOVO product: 21A4 v: ThinkBook 15 G3 ACL serial: <filter>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76530 WIN serial: <filter> UEFI: LENOVO
    v: GQCN29WW(V1.15) date: 11/04/2021
CPU:
  Info: 8-core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP cache:
    L2: 4 MiB
  Speed (MHz): avg: 1500 min/max: 1400/4370 cores: 1: 1400 2: 1400 3: 1400 4: 1400 5: 1800
    6: 1400 7: 1800 8: 1400 9: 1800 10: 1400 11: 1400 12: 1400 13: 1800 14: 1400 15: 1400 16: 1400
Drives:
  Local Storage: total: 506.76 GiB used: 344.4 MiB (0.1%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZALQ512HBLU-00BL2 size: 476.94 GiB
  ID-2: /dev/sda type: USB vendor: Intenso model: Ultra Line size: 29.82 GiB
notebook:~ #
12

Now I counted that after the command “zypper dup” refreshing the repositories does not take much time (I have 3 extra) , but the “packet reading” process takes 3 minutes and more.

time zypper refresh
real 0m0,100s
user 0m0,082s
sys 0m0,020s

13

this is real one

#time zypper refresh
real    0m3,429s
user    0m1,407s
sys     0m0,168s

# inxi -zSMCD
System:
  Kernel: 5.19.2-1-default arch: x86_64 bits: 64 Desktop: KDE Plasma
    v: 5.25.4 Distro: openSUSE Tumbleweed 20220825
Machine:
  Type: Laptop System: HP product: HP ProBook 650 G2 v: N/A serial: <filter>
  Mobo: HP model: 80FD v: KBC Version 22.74 serial: <filter> UEFI: HP v: N76
    Ver. 01.57 date: 07/28/2022
CPU:
  Info: dual core model: Intel Core i5-6200U bits: 64 type: MT MCP cache:
    L2: 512 KiB
  Speed (MHz): avg: 1155 min/max: 400/2800 cores: 1: 800 2: 701 3: 2400
    4: 722
Drives:
  Local Storage: total: 342.81 GiB used: 12.8 GiB (3.7%)
  ID-1: /dev/sda vendor: Lexar model: 240GB SSD size: 223.57 GiB
  ID-2: /dev/sdb vendor: SanDisk model: SD8SN8U-128G-1006 size: 119.24 GiB



Speedtest by Ookla

     Server: xxxxxxxxxxxxxxxxxxx
        ISP: xxxxxxxxxxxxx
    Latency:    12.22 ms   (0.56 ms jitter)
   Download:    95.52 Mbps (data used: 91.9 MB )
     Upload:    57.79 Mbps (data used: 66.6 MB )
Packet Loss:     0.0%
14

zypper cpu time depends on processor model: Intel Core i5-6200U @ 2.30GHz vs AMD Ryzen 5 5600X vs AMD Ryzen 7 5700U [cpubenchmark.net] by PassMark Software

You may run zypper as a service: Tumbleweed zypper dist-upgrade as a systemd service - openSUSE Wiki

Journal summary of one daily run:

Package download: failure due to bad repo. Disabled repo and restarted:

**erlangen:~ #** journalctl -b -5 -u dup -g 'Pakete|Consumed' -o short-monotonic  
  379.404894] erlangen zypper[2871]: Installierte Pakete werden gelesen... 
  381.521938] erlangen zypper[2871]: Die folgenden 1319 Pakete werden aktualisiert: 
  381.523281] erlangen zypper[2871]: Die folgenden 31 Pakete werden den Anbieter ändern: 
  381.523281] erlangen zypper[2871]: Die folgenden 63 NEUEN Pakete werden installiert: 
  381.523281] erlangen zypper[2871]: Die folgenden 22 Pakete werden GELÖSCHT: 
**  381.523281] erlangen zypper[2871]: 1319 Pakete werden aktualisiert, 1 wird zurückgestuft, 63 neue, 22 zu entfernen, 31  Anbieterwechsel, 1 Architekturwechsel. 
  396.272808] erlangen zypper[2871]: Während oder nach der Installation/dem Entfernung von Paketen ist ein Problem aufgetreten: **
**  396.294912] erlangen systemd[1]: dup.service: Consumed 4.137s CPU time.** 
  475.843432] erlangen zypper[3026]: Installierte Pakete werden gelesen... 
  477.417836] erlangen zypper[3026]: Die folgenden 1288 Pakete werden aktualisiert: 
  477.419144] erlangen zypper[3026]: Die folgenden 63 NEUEN Pakete werden installiert: 
  477.419144] erlangen zypper[3026]: Die folgenden 53 Pakete werden GELÖSCHT: 
**  477.419144] erlangen zypper[3026]: 1288 Pakete werden aktualisiert, 1 wird zurückgestuft, 63 neue, 53 zu entfernen, 1 Architekturwechsel. 
  508.938622] erlangen systemd[1]: dup.service: Consumed 4.141s CPU time. 
****erlangen:~ #**

Install:

**erlangen:~ #** journalctl -b -5 -u dupa -g 'Pakete|Consumed' -o short-monotonic  
  524.968046] erlangen zypper[3134]: Installierte Pakete werden gelesen... 
  526.574643] erlangen zypper[3134]: Die folgenden 1288 Pakete werden aktualisiert: 
  526.575795] erlangen zypper[3134]: Die folgenden 63 NEUEN Pakete werden installiert: 
  526.575795] erlangen zypper[3134]: Die folgenden 53 Pakete werden GELÖSCHT: 
  526.575795] erlangen zypper[3134]: 1288 Pakete werden aktualisiert, 1 wird zurückgestuft, 63 neue, 53 zu entfernen, 1 Architekturwechsel. 
  813.038756] erlangen systemd[1]: dupa.service: Consumed 3min 35.144s CPU time. 
**erlangen:~ #**