{'fraction_non_alphanumeric': 0.021479713603818614, 'fraction_numerical': 0.0, 'mean_word_length': 5.712, '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}}
A Comparative Evaluation of Software Rejuvenation Strategies

In this paper we present an experimental comparative study of most of the rejuvenation techniques developed so far, divided into two groups: i) simple approaches: physical node reboot (switch off/on), VM reboot, OS reboot and standalone application restart, and ii) sophisticated methods: OS fast reboot, and application restart with hot standby mode. In our experiments we evaluate the availability and performance overheads incurred by software rejuvenation. We also analyze the selected rejuvenation techniques efficiency to mitigate the aging effects. We inject memory leaks at application level to simulate the aging effects. The results show that the availability and performance overheads introduced by the rejuvenation strategies are specific to the granularity level.