Description of problem: I own a 2 1/2 year old laptop with Pentium M 1,5 GHz, 60 GB harddisk and ATI Graphics. I the harddisk is quite slow, I know that, but it's normally fast enough for normal use. But I noticed that yum-updatesd takes quite a while to start due to the slow disk -- between 5 and 5,5 seconds round about. That's IMHO far to much for a daemon that's started on boottime (thus I disabled it in between). Version-Release number of selected component (if applicable): yum-updatesd-3.0.1-2.fc6 How reproducible: Always Additional Informations: [root@notebook ~]# time /etc/init.d/yum-updatesd start Yum-Updatesd starten: [ OK ] real 0m5.398s user 0m0.514s sys 0m0.126s [root@notebook ~]# /etc/init.d/yum-updatesd stop Yum-updatesd beenden: [ OK ] [root@notebook ~]# time /etc/init.d/yum-updatesd start Yum-Updatesd starten: [ OK ] real 0m0.481s user 0m0.263s sys 0m0.051s [root@notebook ~]#
(In reply to comment #0) > [root@notebook ~]# time /etc/init.d/yum-updatesd start This first run was with cold cache ("echo 3 >/proc/sys/vm/drop_caches"). It's probably a little bit faster during startup as some other things updatesd might need are probably in the cache already, but it's not much faster afaics
Putting some dead simple timing, this is purely due to the various imports which are done. It looks like delaying imports until after we fork could cut the time roughly in half
This isn't just slow old hard disks; it's an issue on my spanking new desktop and laptop systems, too. yum-updatesd is the most visible component of boot time :-(
Improved in yum CVS. Time with cold cache on my laptop is now 2.8 seconds. Cold cache to just start the python interpreter and print hello world is 1.6 seconds. So that seems about as good as we're going to get.