mirror of
https://github.com/GreptimeTeam/greptimedb.git
synced 2025-12-27 00:19:58 +00:00
6e9a9dc333
* refactor(log_store): remove associated type `Namespace` in `LogStore` * fix(test): filter entries * refactor: ignore incomplete parts * refactor: simplify `RawEntryReaderFilter` * chore: avoid cloning * test: add tests for `maybe_emit_entry` * refactor: remove `Namespace` trait and rename `LogStoreNamespace` to `Namespace` * chore: apply suggestions from CR * refactor: refine `entry` method signature * feat: ingore any potential incomplete parts * refactor: rename `namespace` to `provider` * chore: add debug assertion * refactor: associated type `Entry` in `LogStore` * refactor: renamse `namespace` to `provider` * refactor: remove unwrap * refactor: let `remaining_entries` return a optional vector * test: add basic tests for kafka logstore * refactor: move `append` method under `cfg(test)` * refactor: rename `RawEntry` to `Entry` * refactor: rename `CorruptedLogEntry` to `CorruptedEntry` * test: add tests for handling corrupted raw entry stream * refactor: rename `ns` to `provider` * refactor: remove `entry_stream.rs` file * chore: remove unused code * chore: update comments * chore: apply suggestions from CR * chore: update comments * chore: apply suggestions from CR * chore: remove Deref * chore: add comments * fix: ignores tail corrupted data * chore: add comments * fix: add `MIN_BATCH_SIZE` limit
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.