Renamed/tweaked crystal_size -> crystal_thresh

Our crystallization threshold doesn't really describe the bounds of an
object, and I think it's a bit easier to think of it as a threshold for
block compaction.

Heck I've already been calling this the crystallization threshold all
over the code base.

An important change is this bumps the value by 1 bytes, so
crystal_thresh now describes the smallest size of a block our write
strategy will attempt to write.

Heuristically:
- data >= crystal_thresh => compacted into blocks
- data <  crystal_thresh => stored as fragments
This commit is contained in:
Christopher Haster
2023-12-14 12:49:43 -06:00
parent 02d2919130
commit c2e3a391ff
4 changed files with 18 additions and 18 deletions
+1 -1
View File
@@ -295,7 +295,7 @@ struct lfs_config {
lfs_size_t inline_size;
lfs_size_t shrub_size;
lfs_size_t fragment_size;
lfs_size_t crystal_size;
lfs_size_t crystal_thresh;
};
// File info structure