Am Freitag, den 12.06.2009, 08:48 -0700 schrieb Toshio Kuratomi:
On 06/12/2009 08:14 AM, Christoph Wickert wrote:
> Am Freitag, den 12.06.2009, 05:34 +0200 schrieb Kevin Kofler:
>> I don't see what it buys our users if they get one big update over 2 small
>> ones.
>
> In most cases the biggest part (consuming time and cpu cycles) of the
> updates is not installing them but everything else like checking for new
> packages, downloading the metadata,
This portion of the list is saved.
This part happens in the background without user's notice, so this
portion irrelevant.
> calculating dependencies,
> downloading the packages and running the transaction test. Especially
> for small updates this takes much more time than the actual "rpm -U"
> part.
>
But this portion of your list is dependent on the size of the
transaction so it isn't going to halve the time to go from two small
updates to a single large update here.
But this is the portion that requires user interaction, what happens
between the first update notice and the message that all updates were
installed. So from a users POV the time is reduced dramatically. I think
it could even more than halve because scriptlets are only running once
instead of several times.
-Toshio
Regards,
Christoph