Skip to content

Effect of removing Node256 fullness check on add

Laurynas Biveinis edited this page May 15, 2021 · 1 revision

Node256 can never be full if it has to be added to, even if it can be full at other times.

The effect of this removal (baseline, patch) on micro_benchmark_node256 --benchmark_repetitions=9 --benchmark_filter=add.*unodb::db is 0%-6% speedup, highest on small trees, decreasing as trees increase.

Clone this wiki locally