[Bug 1936175] Re: apt hook slows down apt - could this be asynchronous?
Christian Ehrhardt
1936175 at bugs.launchpad.net
Wed Jul 14 07:49:24 UTC 2021
i#m not entirely sure on PathChanged= vs PathModified= but want to hear
an opinion on the general approach first.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-notifier in Ubuntu.
https://bugs.launchpad.net/bugs/1936175
Title:
apt hook slows down apt - could this be asynchronous?
Status in update-notifier package in Ubuntu:
New
Bug description:
Hi,
I was actually looking for needrestart as it has the last messages in an apt transaction and then seems to stall. But I found that it isn't
/etc/apt/apt.conf.d/99needrestart
instead it is the other 99 which is
/etc/apt/apt.conf.d/99update-notifier
I've littered the steps it executes for debugging and found that the
final call to `/usr/lib/update-notifier/apt-check --human-readable`
takes about 4 seconds.
Here at the end of an `apt install --reinstall` of any package.
DEBUG I 07:04:54.330869746
DEBUG II 07:04:54.331734979
DEBUG III 07:04:54.350096999
DEBUG IV 07:04:54.360757929
DEBUG V 07:04:54.376343616
DEBUG VI 07:04:54.379049099
DEBUG VII 07:04:54.386505261
DEBUG VIII 07:04:58.824188091 <<< those 4 seconds
DEBUG IX 07:04:58.826370395
DEBUG IX 07:04:58.827825319
The time varies on system HW and installed packages, but is always at an annoying >1sec.
If not just an automated background install people often wait for apt to complete to be able to do the next steps.
And then apt seeming complete (it is actually) but having this artificial delay makes Ubuntu feel slow every time.
This is only meant to populate /var/lib/update-notifier/updates-
available with some content to be used by the notifier later. I don't
know if there are other consumers of this file, but you'd think that
the motd infrastructure would certainly be ok if this is complete
slightly after the apt transaction.
Somewhere in the back of my mind was that this was tried ...
And what makes me suspicious is at least:
# let the actual update be asynchronous to avoid stalling apt-get
cleanup() { rm -f "$tmpfile"; }
I checked the change-log for it and found bug 1527710 which explains
why - currently - it isn't asynchronous anymore. (The changelog also
explains why I thought to remember this being async, I did that myself
6 years ago). I have to agree all those issues with the asynchronicity
back then were bad, but while the current stall isn't as "breaking" is
is really bad on the "user inconvenience" side of things.
I wanted to file this bug (despite it being tried in the past) to
discuss if we could find a way to disconnect these and make apt fast
again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1936175/+subscriptions
More information about the foundations-bugs
mailing list