The current implementation of the component updater uses a compile-time constant for the time interval it waits between applying successive component updates, when the update response includes updates to several components. The current wait time is 15 minutes.

The component updates are applied sequentially, in a priority order determined by the the order in which components are registered with the component update service.

This algorithm could delay applying updates for components that are queued behind other components which update frequently (daily basis) but the cost of those updates is small.

A change in the update algorithm is suggested, so that the wait time between components is adaptive, and it depends on the cost of the previous component update.

* Update-check all components 6 minutes after browser start.
* Apply the first update immediately; let T be the time this takes.
* for each remaining update {
    * Wait T or 15 minutes, whichever is less.
    * Apply the update.
    * Let T for the next update be the time it took to apply this update.
}
* Wait 6 hours then repeat this process.