{'fraction_non_alphanumeric': 0.02444987775061125, 'fraction_numerical': 0.0024449877750611247, 'mean_word_length': 4.808510638297872, '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 Multi-OS Cross-Layer Study of Bloating in User Programs, Kernel and Managed Execution Environments

We present a study of bloating across the software stack. We study user-level programs, OS kernels and Java virtual machine. We employ: (1) static measurements to detect limits to debloating, and (2) dynamic measurements to detect how much of the code available to a program is utilized under typical payloads. We incorporate an ultra-light weight tracing procedure in a whole-system emulator to measure the bloat in kernel. We measure the amount of kernel code that executes during the boot process and during the execution of popular system calls. Our findings show that bloating is pervasive and severe. A significant fraction of code across the software stack is never executed and provides scope for debloating.