crimson profiling by fio metrics
4 KB fio test, total 10 round, each round 600s.
single OSD instance
deployed by vstart.sh
crimson-seastore
master
(commit ID bd94f885ab22c9974301f1caca91aea37ecc8edc
) + #42957
fio rbd_write.fio configuration
[global]
ioengine=rbd
clientname=admin
pool=rbd
rbdname=fio_test
rw=randwrite
bs=4K
runtime=600
numjobs=4
direct=1
group_reporting
[rbd_iodepth32]
iodepth=64
crimson Build configuration
./do_cmake.sh -DWITH_SEASTAR=ON -DWITH_MGR_DASHBOARD_FRONTEND=OFF -DCMAKE_BUILD_TYPE=RelWithDebInfo
[build]$ MDS=0 MGR=1 OSD=1 MON=1 ../src/vstart.sh -n --without-dashboard --seastore -X --crimson (only enable error output)
[build]$ ../../cbt/tools/crimson/seastore_fio_run.sh
[build]$ ../../cbt/tools/crimson/seastore_metrics_analyze.py
...
Transaction invalidate/commit ratio by src
Transaction invalidate/commit ratio for each src, elaborated by the extent-type that caused the conflicts
Transaction invalidated/committed effort ratio for each src
Write amplification at different layers
Write amplification at FRESH_EXTENTS+DELTA layer, elaborated by src, and elaborated by the extent-type that was committed