Skip to content

Instantly share code, notes, and snippets.

@liu-chunmei
Last active August 28, 2021 05:09
Show Gist options
  • Save liu-chunmei/45c56b0d1dcc27172f9c03fc06476035 to your computer and use it in GitHub Desktop.
Save liu-chunmei/45c56b0d1dcc27172f9c03fc06476035 to your computer and use it in GitHub Desktop.

crimson profiling by fio metrics

Scenario

  • 4 KB fio test, total 10 round, each round 600s.
  • single OSD instance
  • deployed by vstart.sh
  • crimson-seastore

version

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 

crimson Deployment

[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
...

Cache basics

cache_usage

cache_hit_access_ratio_by_src

Tree basics

tree_depth

tree_operations

Transaction invalidate/commit ratio by src

trans_invalidate_committed_ratio_by_src---inaccurate

Transaction invalidate/commit ratio for each src, elaborated by the extent-type that caused the conflicts

trans_invalidate_committed_ratio_by_extent---MUTATE

trans_invalidate_committed_ratio_by_extent---READ

trans_invalidate_committed_ratio_by_extent---CLEANER

Transaction invalidated/committed effort ratio for each src

trans_invalidate_committed_ratio_by_effort---accurate---CLEANER

trans_invalidate_committed_ratio_by_effort---accurate---MUTATE

trans_invalidate_committed_ratio_by_effort---accurate---READ

Write amplification at different layers

write_amplification_overall

Write amplification at FRESH_EXTENTS+DELTA layer, elaborated by src, and elaborated by the extent-type that was committed

write_amplification_by_extent---MUTATE

write_amplification_by_extent---CLEANER

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment