https://bugs.kde.org/show_bug.cgi?id=466671
--- Comment #3 from Jonathan Wakely <zi...@kayari.org> --- (In reply to Jonathan Wakely from comment #0) > SUMMARY > > When opening discover from the systray widget when it shows updates are > available, it takes 30+ seconds to show the available updates. The previous > cause of slowness was supposed to have been fixed (Bug 457408) but I see no > improvement in the default use case of "click on the systray widget when it > shows updates". Maybe something got fixed in the KNewStuff backend, but > there's another cause of slowness, and it has the same symptom: the > "Fetching updates..." progress bar goes to about 97% immediately, then stops > for 30 seconds. > > The same slowness happens when clicking the "Refresh" button. > > > STEPS TO REPRODUCE > 1. plasma-discover --mode Update > 2. click Refresh > 3. waaaaaaaiiiiiiiiiiiiiit > > OBSERVED RESULT > > Slow > > EXPECTED RESULT > > More fastish! > > SOFTWARE/OS VERSIONS > Operating System: Fedora Linux 37 > KDE Plasma Version: 5.27.1 > KDE Frameworks Version: 5.103.0 > Qt Version: 5.15.8 > Kernel Version: 6.1.11-200.fc37.x86_64 (64-bit) > Graphics Platform: X11 > Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz > Memory: 31.1 GiB of RAM > Graphics Processor: Mesa Intel® UHD Graphics 630 > > ADDITIONAL INFORMATION > > $ plasma-discover --listbackends > Available backends: > * fwupd-backend > * kns-backend > * flatpak-backend > * packagekit-backend > > By a process of elimination I found that it's the packagekit backend that's > slow. Clicking Refresh after running it as 'plasma-discover --mode Update > --backends fwupd-backend,flatpak-backend,kns-backend' finished almost > immediately, and any combination of backends that doesn't involve > packagekit-backend is fast. Any combination that involves packagekit-backend > (including just that one, i.e. --backends packagekit-backend) takes 30+ > seconds. > > > DNF and PackageKit can both refresh their package lists in far less time > than Discover can: > > $ time pkcon refresh > Refreshing cache [=========================] > Loading cache [=========================] > Finished [=========================] > > real 0m0.352s > user 0m0.007s > sys 0m0.007s Although `pkcon refresh` takes less than a second, `pkcon refresh force` is much slower: $ time pkcon refresh force Refreshing cache [=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Downloading repository information[=========================] Loading cache [=========================] Querying [=========================] Loading cache [=========================] Finished [=========================] real 0m33.664s user 0m0.024s sys 0m0.013s It seems that discover is doing the equivalent of `refresh force` when you click on the systray widget, even if it's recently done a refresh. That's why it's always so slow. -- You are receiving this mail because: You are watching all bug changes.
