Skip to content

[benchmark] Fix stale throughput and duration docs in cluster README #8752

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
thswlsqls wants to merge 1 commit into from
Closed

[benchmark] Fix stale throughput and duration docs in cluster README #8752

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions paimon-benchmark/paimon-cluster-benchmark/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ This is the cluster benchmark module for Paimon. Inspired by [Nexmark](https://g

### Run Benchmark
* Run `paimon-benchmark/bin/run_benchmark.sh <query> <sink>` to run `<query>` for `<sink>`. Currently `<query>` can be `q1` or `all`, and sink can only be `paimon`.
* By default, each query writes for 30 minutes and then reads all records back from the sink to measure read throughput.
* By default, each query writes the number of rows configured by `row-num` in `paimon-benchmark/queries/queries.yaml` and then reads all records back from the sink to measure read throughput.

## Queries

Expand All @@ -45,7 +45,7 @@ Results of each query consist of the following aspects:
* Throughput (rows/s): Average number of rows inserted into the sink per second.
* Total Rows: Total number of rows written.
* Cores: Average CPU cost.
* Throughput/Cores: Number of bytes inserted into the sink per second per CPU.
* Throughput/Core: Number of rows inserted into the sink per second per CPU core.
* Avg Data Freshness: Average time elapsed from the starting point of the last successful checkpoint.
* Max Data Freshness: Max time elapsed from the starting point of the last successful checkpoint.

Expand Down