We introduce a delete-heavy benchmark to allow investigating and optimising TypeDB's delete path.
Run using:
bazel run //read-write:benchmark-runner -- --database=typedb --address=127.0.0.1:1729 --config=read-write/config/medium-delete-benchmark.yml
Note: In TypeDB 2.21.1,aAfter 3 iterations, profiling shows 70% of time is spent on seek() on the storage layer, indicating a clear bottleneck or issue to be resolved.
What are the changes implemented in this PR?
Rename run to action throughout
Introduce deletePerson action, which randomly samples people ID's from the range of inserted people and deletes them if they exist (they may already be deleted so this is a no-op)
What is the goal of this PR?
We introduce a delete-heavy benchmark to allow investigating and optimising TypeDB's delete path.
Run using:
Note: In TypeDB 2.21.1,aAfter 3 iterations, profiling shows 70% of time is spent on
seek()on the storage layer, indicating a clear bottleneck or issue to be resolved.What are the changes implemented in this PR?
runtoactionthroughoutdeletePersonaction, which randomly samples people ID's from the range of inserted people and deletes them if they exist (they may already be deleted so this is a no-op)