Repository navigation

Dirty memory ratio and size can trigger ckpt - #406

Merged

githubzilla merged 15 commits into

mainfrom

dirty_memory_trigger_ckpt

Feb 25, 2026

Merged

Dirty memory ratio and size can trigger ckpt#406
githubzilla merged 15 commits into
mainfrom
dirty_memory_trigger_ckpt

Commits on Feb 12, 2026
- Initial commit
  githubzilla
  committed
  108bca1
- Trigger ckpt only when both ratio and size exceeded
  githubzilla
  committed
  d88a237
- Only use dirty memory size to trigger ckpt
  githubzilla
  committed
  4235db2
- fix clang-format
  githubzilla
  committed
  7ecd512
- Move dirty_memory config to tx_service_init.cpp
  githubzilla
  committed
  13dbcc1
- Fix comments
  githubzilla
  committed
  df9bfb6
Commits on Feb 13, 2026
- Leverage CcShard::NotifyCkpt()
  githubzilla
  committed
  4e454e2
- Guarante memory order of request_ckpt_ and notify
  githubzilla
  committed
  a34a21d
- Add checkpoint_min_interval
  githubzilla
  committed
  87efd56
- Add comments
  githubzilla
  committed
  bd6508c
Commits on Feb 14, 2026
- Make ckpt min interval default value smaller than the de-facto ckpt interval used when test
  githubzilla
  committed
  5619eb6
Commits on Feb 20, 2026
- Seperate the ckpt request interval with ckpt interval
  githubzilla
  committed
  9b336eb
- Fix comments
  githubzilla
  committed
  4aabbe8
- Fix compile warning
  githubzilla
  committed
  75885c1
Commits on Feb 21, 2026
- Init last_checkpoint_request_ts_
  githubzilla
  committed
  51c683e