cmd/pebble: add many more benchmarks about pebble HOT 4 CLOSED

The benchmarks we have now with pebble ycsb are pretty good. One thing I'm trying to figure out is what numbers to look at particularly for workloads involving writes. Here's my high level proposal.

The first step will be find the "peak sustainable throughput". That metric could be found by an unbounded search on the rate limit argument to pebble ycsb. A workload would be deemed sustainable if, on a prefilled large DB, it can run until pending compaction bytes converges without hitting any stall/stop limits. If pending compaction bytes keeps increasing meaningfully beyond some period of time, or stall/stop limits are ever reached, we can declare the throughput is too high.

The next step is to establish the latency/throughput curve. We can run workloads at a few different throughputs between 0 and the peak sustainable throughput. We can record read/write p50/p99 latencies and graph the results. Here's an example graph I'd like to make, taken from the YCSB paper.

Then the third step is automation allowing us to run an A/B test on different Pebble binaries or on Pebble vs. RocksDB. Maybe also a way to quantify improvement/regression (this is easy for peak sustainable throughput, but not so easy for the latency/throughput curve).

from pebble.

The next step is to establish the latency/throughput curve. We can run workloads at a few different throughputs between 0 and the peak sustainable throughput. We can record read/write p50/p99 latencies and graph the results. Here's an example graph I'd like to make, taken from the YCSB paper.

It might be reasonable for this step to have a warm-up phase until cache is populated and pending compaction bytes has stabilized. I guess the latency profile will stabilize afterwards.

from pebble.

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it
in 10 days to keep the issue queue tidy. Thank you for your
contribution to Pebble!

from pebble.

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it
in 10 days to keep the issue queue tidy. Thank you for your
contribution to Pebble!

from pebble.