search

mitdbg / treeline

An update-in-place key-value store for modern storage.
MIT License
132 stars 18 forks source link

Report requests per second in range scans (YCSBR) #18

Closed geoffxy closed 2 years ago

geoffxy commented 3 years ago

For range scan workloads, we currently report the number of records processed per second. However in YCSB, the standard metric is requests per second. We should switch over to requests per second to avoid confusion when others look at the numbers.

geoffxy commented 3 years ago

Let's just clearly indicate in the paper that we're reporting # of records scanned. Fixing this is not worth the time, given our constraints.

geoffxy commented 3 years ago

Reopening as we should still add an option in YCSBR to report requests/second to avoid confusion in the results.

geoffxy commented 2 years ago

YCSBR v4.0.0 will report throughput in thousands of records per second and thousands of requests per second. For workloads with no range scans, these values will be the same.