greptimedb

mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-01-05 21:02:58 +00:00

Files

dimbtp 3b89b9ddd8 refactor: move database client to test (#3820 )

* remove `Database` in `cli export`

* move `Database` to tests-integration

* fix clippy

* move `DatabaseClient` along with `Database`

* `cli export` now use http api

* add TODO for `tests-integration` dependencies

* cleanup code

* 'cli export' test use http api

* remove unsed dependencies in cmd crate

* apply review comments and clean code

* remove unused methods

Signed-off-by: tison <wander4096@gmail.com>

---------

Signed-off-by: tison <wander4096@gmail.com>
Co-authored-by: tison <wander4096@gmail.com>

2024-05-01 05:55:13 +00:00

config

feat: introduce wal benchmarker (#3446 )

2024-04-03 03:16:05 +00:00

src

refactor: move database client to test (#3820 )

2024-05-01 05:55:13 +00:00

Cargo.toml

refactor: move database client to test (#3820 )

2024-05-01 05:55:13 +00:00

README.md

feat: introduce wal benchmarker (#3446 )

2024-04-03 03:16:05 +00:00

README.md

Benchmarkers for GreptimeDB

Wal Benchmarker

The wal benchmarker serves to evaluate the performance of GreptimeDB's Write-Ahead Log (WAL) component. It meticulously assesses the read/write performance of the WAL under diverse workloads generated by the benchmarker.

How to use

To compile the benchmarker, navigate to the greptimedb/benchmarks directory and execute cargo build --release. Subsequently, you'll find the compiled target located at greptimedb/target/release/wal_bench.

The ./wal_bench -h command reveals numerous arguments that the target accepts. Among these, a notable one is the cfg-file argument. By utilizing a configuration file in the TOML format, you can bypass the need to repeatedly specify cumbersome arguments.