On Thu, Apr 21, 2022 at 12:45:48PM +0200, Miroslav Suchý wrote: > Dne 20. 04. 22 v 8:55 Jaroslav Mracek napsal(a): > > > > > > I've gotta ask... How much memory does the new dnf daemon take while idle? > After installation: > Memory: 1.6M > CPU: 23ms > > After upgrade of few packages: > Memory: 917.6M > CPU: 1min 44.767 > > This is a lot. To dive deep. `top` reports VIRT: 797232, RES: 186596 182 MB RSS is a lot, but should be acceptable on today's systems, as long as it's transient. Ideally: - dnf-daemon would be dbus-activated and exit-on-idle after a suitable timeout (the timeout can be something like 15 minutes, so that it's not needlessly respawned if somebody is doing some interactive work. It just shouldn't stay around "forever".) - If it is spawned also by things like command-not-found, it would need to start quickly. Possibly some caching of the repo state would need to be done. (Though maybe not. In a container where I'm testing this, i.e. with just the basic repos and a few packages, microdnf loads the metadata in <1s. If it stays <1s, this should be good enough.) Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
