Skip to content

Commit 0d0cded

Browse files
committed
final report: clarify reasons for small tables being faster
1 parent ce03e4b commit 0d0cded

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

doc/final-report/final-report.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1361,7 +1361,8 @@ turn out to be the `cabal` process and not the benchmark process.
13611361

13621362
By the way, we also get excellent speed with the 10 M entry table: 150 k
13631363
ops/sec, much more than the circa 86 k ops/sec we get with the 100 M entry
1364-
table. The reason is that for smaller tables there is less merging work to do.
1364+
table. The reason is that for smaller tables there is less work to do generally:
1365+
less merging work, fewer runs, fewer Bloom filters.
13651366

13661367
## The upsert benchmarks
13671368

0 commit comments

Comments
 (0)