Use system dnf cache?

[mikhailnov]

Every launch of dnfdragora takes quite a lot of time to at least make cache and maybe update metadata, why can't it use system dnf cache without updating it, provided that dnf-makecache.timer is enabled by default? Just to speedup things a lot. Or maybe update metadata in the background.

[anaselli]

Are you using Group or all view? first needs more local caching in fedora since groups are not managed as in mageia.

[anaselli]

Group caching apart, "caching time" is required since those data are sent from dnf-daemon as you can see when progress bar (or reading logs) increases

[anaselli]

and that is performed in background... but dnfdragora has nothing to show yet... i wasn't able to speed up that part, ideas or help are welcome :)

[mikhailnov]

I am using Group view, all packages do have Group tag in ROSA. Yeah, I already understood, some time is required to load information about all packages. Do dnfdaemon+dnfdragora make a separate cache here? Do they use the cache that is updated by dnf-makecache.timer or a separate one?

[mikhailnov]

I installed a fresh build of dnfdragora by running sudo dnf in --refresh dnfdragota-gtk, so I had a fresh system cache at the moment of the first launch of dnfdragora, but dnfdragora started to refresh metadata on the first launch and that took a lot of time on my CPU. So, it either uses a separate cache (what for?) or incorrectly handles such case.

[anaselli]

dnfdragora has also a local "cache" with all the package and groups, though group caching should not be a problem for openmandriva if, as i think, has groups like mageia. But as said i tried to split and optimize that code without gain that much... maybe a better software engineer could help here? Blocking query where slow as well but dialgo was ugly, now dnfdragora waits for data, but time is almost the same...

[Conan-Kudo]

We're already using the system cache through dnfdaemon, so this is not actually an issue. The daemon does need to load the cache into memory and enumerate everything, which takes some time.

[mikhailnov]

4 апреля 2021 г. 17:56:06 GMT+03:00, "Neal Gompa (ニール・ゴンパ)" ***@***.***> пишет:

We're already using the system cache through dnfdaemon, so this is not actually an issue. The daemon does need to load the cache into memory and enumerate everything, which takes some time.

Then why did it update metadata on the first launch? Metadata was about 10-30 min old

[anaselli]

Sorry i can't get what you mean.

[wojnilowicz]

Sorry i can't get what you mean.

I believe that the issue here is as follows:

STEPS TO REPRODUCE IN A TERMINAL:

1. dnf clean all (this cleans user dnf cache)
2. sudo dnf clean all (this cleans system dnf cache)
3. sudo dnf makecache (this refreshes system dnf cache by downloading full metadata)
4. dnfdragora (this indirectly refreshes user dnf cache by downloading full metadata again)

BEHAVIOR:
dnfdragora refreshes user dnf cache by downloading full metadata again which takes significant amount of time.

EXPECTED BEHAVIOR:
dnfdragora should use system dnf cache or allow choosing between using either user or system dnf cache.

ADDITIONAL INFORMATION:

1. Fedora 35 KDE
2. sudo systemctl disable dnf-makecache.timer
3. sudo systemctl disable dnf-system-upgrade
4. sudo systemctl stop dnfdaemon
5. sudo dnf remove dnfdragora-updater

Please consider reopening, and fixing this issue.

[anaselli]

As far as I can say with commit ce29aca45d14f9f45d512d3fc5eb6b35db1ab19d and 674f768e10d7f5d90a9069d2a9c89da7a8239e09 We improved metadata management, maybe bugs can be present. We need help to understand how to change the behavior if it is wrong. Patches are also welcome

[wojnilowicz]

As far as I understand, the commits that you mention, don't touch the issue explained here. Maybe you could require a password for refreshing metadata similarly to the way you require a password for installing/updating/removing a package.

[anaselli]

password is needed only if dnfdaemon needs right escalation.
Check should be here and called here.