Since MIO use devdax, first you need to expose Cylon as devdax device by running
daxctl reconfigure-device --mode=devdax --force dax0.0- This experiment is comparing Cylon vs QEMU access latency using MIO. The provided script will run, process, and plot the result for you. You can run it by using
run-figure3.shand check the plot inside../plot/figure3.pdf.cd run bash run-figure3.sh
- This experiment is comparing Cylon vs CMM-H latency distribution using MIO. The provided script will run, process, and plot the result for you. You can run it by using
run-figure6.shand check the plot inside../plot/mio-cmmh-cylon-t4.pdf.cd run bash run-figure6.sh
This experiment is to see the impact of different eviction policies on Cylon latency using MIO. You must reboot/restart the VM between different eviction policies.
- Run this script once per policy with a different RUN_TAG.
RUN_TAG=FIFO-NAND2 ./run-figure9.sh RUN_TAG=LIFO-NAND2 ./run-figure9.sh RUN_TAG=CLOCK-NAND2 ./run-figure9.sh RUN_TAG=S3FIFO-NAND2 ./run-figure9.sh
- After that you can run
Check the graph result in
gnuplot plot-fig9.gp
../plot/mio-eviction.pdf
- This experiment is to see the impact of prefetching degree on Cylon latency using MIO. The script will run, process, and plot the result for you. To get the result, you just need to run this and check the plot inside
../plot/prefetching-fifo.pdf:cd run bash run-figure10.sh