On Wed, Aug 29, 2007 at 01:44:31PM -0400, Matthew Miller wrote:
> On Wed, Aug 29, 2007 at 11:15:00AM -0500, Michael E Brown wrote:
> > > I think maybe a more obvious change is to only add the fireware
> > > packages if the user has done "yum update" without any package name
> > > arguments (or with arguments that match the firmware package names).
> > This sounds fine to me. Can you suggest how I might accomplish this from
> > my plugin?
>
> What's the speed penalty on each yum update run?
Firmware-tools code to generate the list of deps:
typical Non-Dell system: 0.2s
typical Dell system : 1.3s
Yum depsolving overhead:
typical Non-Dell system: 0.2s
typical Dell system : 4.3s
total added overhead:
typical Non-Dell system: 0.4s
typical Dell system : 5.6s
The Dell system used above was a little bit older laptop (D500 -
1.3Ghz), and the non-dell system was a newer Athlon, so I suppose it
isnt a great benchmark.
The list of package names it adds is usually about 20 elements long on
non-dell (basically one for each lspci entry), and 42 on a Dell system
(one for each lspci, one for a system-specific lspci entry, one for
system bios and one for system bmc).
This may potentially grow in the future, as I add USB and SCSI firmware
bootstrap.
--
Michael
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
