In the case of BGP, after an update has been received, the time taken for the best path operation is a direct consequence of the BGP table size based on the layout of the network. This can potentially add many minutes to the overall service-restoration time where it is based on BGP convergence.
This dependency on BGP table size can be alleviated almost completely by the use of techniques such as prefix-independent rewrites within the MSE device's BGP implementation. Prefix-independent rewrite uses a separate table to store common adjacency information shared by multiple prefixes that are linked to it, as opposed to storing this information within every single entry in the forwarding table.
By using this approach, when an adjacency change is necessary, it is a simple matter of updating the common adjacency information once, rather than the size of the BGP table, thus keeping the convergence time a constant, regardless of the size of the network topology involved.