On Wed, Jan 28, 2009 at 10:32 PM, Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx> wrote: > Ralf Corsepius wrote: >> >> Jesse Keating wrote: >>> >>> Try doing updates on a netbook, >> >> I own one - Typical "yum update" times are in the order of "very few" >> minutes at average. > > Looking only at install times... > > Asus EEE 900A (SSD): 3m40s > HP xw4400 Workstation (SATA platter): 1m25s > > ...and the latter did kernel-devel as well as kernel, kernel-headers and > kernel-firmware, plus it also had to remove a kmod-nvidia. (Times are > approximate.) > > ...so the SSD is about 3x slower or more (especially as I notice > kernel-devel took the desktop the longest). > >>> Yum isn't really the problem here, it's the >>> rpms themselves, constantly doing ldconfigs, cache updates, tonnes of >>> hardlinking, etc... >> >> From what I experience, SELinux policy updates are by far means the most >> resource intense/most time consuming part of updating. > > Really? For me, it's always OOo updates... 100 MB in a single package? > (What's worse is that OOo can't be updated while running... it doesn't > crash, but it becomes unable to save; bad news if you forgot to save first. > That and Firefox are the only things I'm aware of with that problem, but at > least with FF it only breaks typing addresses into the address bar.) > > Whereas selinux is a 2.0 MB package :-). Its not about the filesize but about the scripts that run on upgrade. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
