{'fraction_non_alphanumeric': 0.009138381201044387, 'fraction_numerical': 0.0, 'mean_word_length': 5.185483870967742, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Updating routing tables after resource failure in a distributed computer network

This paper is an analysis of overhead required by the MERIT routing table update algorithm after failure of a single network resource. The number of update messages sent by each node during the update process is used as the measure of update overhead. Both synchronous behavior and asynchronous behavior of the MERIT algorithm are considered. The number of messages required for synchronous update is shown to be an upper bound for the number of messages required if update occurs asynchronously. The effect of network topology on update overhead is discussed. Finally, some implementation suggestions aimed at minimizing looping of messages during routing table update are presented.