Data underlying the PhD thesis: Accelerating Programmer-Friendly Intermittent Computing (Chapter 6) (software)

Data underlying the PhD thesis: Accelerating Programmer-Friendly Intermittent Computing (Chapter 6)

The doi above is for this specific version of this dataset, which is currently the latest. Newer versions may be published in the future. For a link that will always point to the latest version, please use
doi: 10.4121/22259011

Datacite citation style:

Vito Kortbeek; Sourav Mohapatra; Saad Ahmed; Przemyslaw Pawelczak (2023): Data underlying the PhD thesis: Accelerating Programmer-Friendly Intermittent Computing (Chapter 6). Version 1. 4TU.ResearchData. software. https://doi.org/10.4121/22259011.v1

Other citation styles (APA, Harvard, MLA, Vancouver, Chicago, IEEE) available at Datacite

Software

usage stats

321

views

downloads

categories

Computer Software

keywords

battery-free, intermittent, memory, non-volatile main memory

licence

CC0

export as...

RefWorks, BibTeX, Reference Manager, Endnote, DataCite, NLM, DC, CFF

by Vito Kortbeek

, Sourav Mohapatra , Saad Ahmed , Przemyslaw Pawelczak

This is the archive for Chapter 6 of the PhD thesis named "Accelerating Programmer-Friendly Intermittent Computing" by Vito Kortbeek.

Rationale

Intermittently operating embedded computing platforms powered by energy harvesting must frequently checkpoint their computation state. Using non-volatile main memory significantly reduces the checkpoint size but at the cost of increasing the checkpoint frequency to cover WAR dependencies. Additionally, non-volatile memory is significantly slower to access. Both of these challenges are addressed by the architecture proposed in Chapter 6, greatly increasing performance.

Archive Structure

This archive consists of the software to emulate the system (`icemu/plugins`), and the LLVM toolchain used to compile applications (`llvm`). The code can be built and run using the development docker container in the `docker` directory. To build all the benchmarks, execute the `run.sh` script within the `benchmarks` directory. Run the respective Jupyter Notebook in the `plotting` directory to analyze the results.

history