Name: nvthreads
Owner: Hewlett Packard Enterprise
Description: null
Created: 2016-08-17 02:38:56.0
Updated: 2017-09-18 06:21:31.0
Pushed: 2017-08-02 20:45:43.0
Homepage: null
Size: 197558
Language: C
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
Terry Hsu «terryhsu@purdue.edu»
Helge Bruegner «helge.bruegner@tum.de»
Indrajit Roy «indrajitroy@google.com»
Kimberly Keeton «kimberly.keeton@hpe.com»
Patrick Eugster «p@dsp.tu-darmstadt.de»
NVthreads is a drop-in replacement for the popular pthreads library that adds persistence to existing multi-threaded C/C++ applications. NVthreads infers consistent states via synchronization points, uses the process memory to buffer uncommitted changes, and logs writes to ensure a program?s data is recoverable even after a crash. NVthreads? page level mechanisms result in good performance: applications that use NVthreads can be more than 2× faster than state-of-the-art systems that favor fine-grained tracking of writes. After a failure, iterative applications that use NVthreads gain speedups by resuming execution.
https://github.com/HewlettPackard/nvthreads
NVthreads is still under development. Please use NVthreads at your own risk. Do not deploy this research prototype to your production software before verifying the correctness and performance of your ported apps. Also, please use the master branch only, other branches are unstable research prototypes.
Install the following packages:
apt-get install gcc-multilib
apt-get install g++-multilib
apt-get install libc6-dev-i386 (if you need 32-bit nvthreads)
Install dummy_nvmfs: https://github.com/HewlettPackard/dummy_nvmfs
NOTE: For simple testing of NVthreads, this step may be skipped, so long as the path /mnt/ramdisk/nvthreads/ exists. Be aware that there will be no delays for each NVM write in this case.
Clone NVthreads repo:
clone https://github.com/HewlettPackard/nvthreads
Create nvmfs with 1000ns delays:
This step is only necessary if using dummy_nvmfs from step 1.
NVthreads/
nvmfs1000
Build NVthreads:
NVthreads/src/
libnvthread.so
Build the recovery test program:
NVthreads/tests/recover/
Run the test:
Note: To start with a clean NVthreads environment, before beginning a test, delete the /tmp/nvlib.crash file, if it exists.
cover_int.o //will abort
cover_int.o //will recover data from previous run
apps/: The applications cases for NVthreads.
- datagen/: generates data from kmeans inputs.
- kmeans/: implementation of the kmeans algorithm.
- phoenix-recovery: kmeans recovery evaluation
- pagerank/: implementation of the well-known page rank algorithm.
- tokyocabinet-1.4.48: Tokyo Cabinet evaluation.
docs/: Published reserach paper for the NVthreads design rationale.
dummy_nvmfs: https://github.com/HewlettPackard/dummy_nvmfs
eval/: Benchmark evaluation
datasets/: please save input data for benchmarks in this directory
tests/: this directory contains Phoenix and PARSEC benchmarks
src/: The core of NVthreads library
source: source code
include: header file
tests/: Simple test cases for NVthreads library
third-parties/:
atlas/: https://github.com/HewlettPackard/Atlas
dthreads/: https://github.com/emeryberger/dthreads
mnemosyne/: http://research.cs.wisc.edu/sonar/projects/mnemosyne/
If you use NVthreads, please cite our reearch paper published at EuroSys 2017, included as doc/nvthreads-eurosys.pdf.
@InProceedings{nvthreads,
author = {Hsu, Terry Ching-Hsiang and Bruegner, Helge and Roy, Indrajit and Keeton, Kimberly and Eugster, Patrick},
title = {{NVthreads: Practical Persistence for Multi-threaded Applications}},
booktitle = {Proceedings of the 12th ACM European Systems Conference},
year = {2017},
series = {EuroSys 2017},
address = {New York, NY, USA},
publisher = {ACM},
doi = {10.1145/3064176.3064204},
isbn = {978-1-4503-4938-3},
location = {Belgrade, Republic of Serbia},
url = {http://dl.acm.org/citation.cfm?doid=3064176.3064204},
}