Skip to content

Latest commit

 

History

History
75 lines (52 loc) · 3.39 KB

R3-VLDB-Experiments.md

File metadata and controls

75 lines (52 loc) · 3.39 KB
Raw

R3:Record-Replay-Retroaction (VLDB'23)

This document contains instructions to run experiments in our VLDB'23 paper:

Qian Li, Peter Kraft, Michael Cafarella, Çağatay Demiralp ,Goetz Graefe, Christos Kozyrakis, Michael Stonebraker, Lalith Suresh, Xiangyao Yu, and Matei Zaharia

R3: Record-Replay-Retroaction for Database-Backed Applications

Proc. of the VLDB Endowment (PVLDB), Volume 16, Vancouver, BC, Canada, 2023.

Most record/replay/retroaction code can be found in the following files:

You can find benchmark source code in the following places:

Preparation

Let's first install some dependencies:

sudo apt install openjdk-11-jdk maven libatomic1

Then, download this repository:

git clone https://github.com/DBOS-project/apiary.git
git checkout r3-exp

Next, let's compile Apiary. In the Apiary root directory, run:

mvn -DskipTests package

Then, let's start Postgres from a Docker image. We recommend you configure Docker so it can be run by non-root users.

scripts/initialize_postgres_docker.sh

We use Vertica as the data recorder. For convenience, ye can also run it in a Docker:

scripts/initialize_vertica_docker.sh

Running Experiments

To execute workloads with R3 capturing:

java -jar target/apiary-bench-exec-fat-exec.jar -b retro -s <workload: moodle, wordpress, tpcc> -notxn -d <duration: 60 sec> -p1 <read ratio: 90> -p2 <write ratio: 10> -retroMode 0 -bugfix none -mainHostAddr <postgres server address> -i <request arrival interval: 2000 us>

To execute the no-record baseline, you can simply add -noProv to the above command. This baseline does not record any data to the recorder.

Then, you can replay the recorded trace (from the command you just executed) and test the replay performance:

java -jar target/apiary-bench-exec-fat-exec.jar -b retro -s <workload: moodle, wordpress, tpcc> -notxn  -retroMode 2 -bugFix none -execId <the first request ID: query it from the data recorder> -mainHostAddr <postgres server address>

To test the performance of the sequential baseline, you can simply add -seqReplay to the above command and re-execute.

After that, for Moodle and WordPress, you can replay the recorded trace with bugfixed code. You need to specify which bugfix you want to use:

java -jar target/apiary-bench-exec-fat-exec.jar -b retro -s <workload: moodle, wordpress, tpcc> -notxn  -retroMode 2 -bugFix <moodle: subscribe, wordpress: comment, option> -execId <the first request ID: query it from the data recorder> -mainHostAddr <postgres server address>

Finally, you can test the performance of our selective retroactive execution, by simply specifying -retroMode 3 in the above command.