Automated Systems Benchmarking Across Reboots

Throughout a benchmarking campaign, especially in the area of systems benchmarking, invoking one or multiple reboots of the system can be very beneficial. This, for instance, applys to campaigns that are testing different kernel configurations. For better usability and a smaller chance of errors it is recommended to automate the campaign. Unfortunately the most common mechanism for automation in UNIX-like systems, which is the shell script, can not make a process continue after a reboot from the point it left off before the reboot.This means that developers have to come up with their own solutions for automating a benchmarking campaign that runs across multiple reboots. And this can be very tricky because of the complexity such a manually implemented mechanism has to adopt should the developer decide to expand their campaign. Rising complexity possibly results in high programming effort, bad readability and unsatisfying results. Consequently, the goal of this thesis is to introduce a more general solution to this problem which preferably reduces the effort for the benchmarking campaign developer, maintains the campaign structure and is employable in many different use-cases.

(Bachelorverteidigung)