Skip to content

Commit 1b5ce13

Browse files
committed
mzbench: remove
This is just a proposal for now, but I wanted to surface the amount of complexity and duplication in mzbench. What pieces do we need to keep? What I've heard is: * A replacement for the avro-insert/avro-upsert benchmarks that is easy to use locally. * Parallelization of kgen to replace the kafka-avro-generator wrapper.
1 parent 123fd2e commit 1b5ce13

File tree

98 files changed

+0
-5838
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

98 files changed

+0
-5838
lines changed

bin/mzbench

Lines changed: 0 additions & 14 deletions
This file was deleted.

ci/test/pipeline.template.yml

Lines changed: 0 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -186,33 +186,6 @@ steps:
186186
run: ci
187187
timeout_in_minutes: 30
188188

189-
- id: aggregations-benchmark
190-
label: "aggregations benchmark sanity check"
191-
depends_on: build-x86_64
192-
plugins:
193-
- ./ci/plugins/mzcompose:
194-
composition: aggregations
195-
run: ci
196-
timeout_in_minutes: 10
197-
198-
- id: avro-upsert-benchmark
199-
label: "avro upsert benchmark sanity check"
200-
depends_on: build-x86_64
201-
plugins:
202-
- ./ci/plugins/mzcompose:
203-
composition: avro-upsert
204-
run: ci
205-
timeout_in_minutes: 10
206-
207-
- id: kafka-sink-avro-debezium-benchmark
208-
label: "kafka sink (avro debezium) benchmark sanity check"
209-
depends_on: build-x86_64
210-
plugins:
211-
- ./ci/plugins/mzcompose:
212-
composition: kafka-sink-avro-debezium
213-
run: ci
214-
timeout_in_minutes: 10
215-
216189
- id: tb
217190
label: tb
218191
depends_on: build-x86_64

doc/developer/mzbench.md

Lines changed: 0 additions & 126 deletions
This file was deleted.

misc/perf-dash/app/Dockerfile

Lines changed: 0 additions & 20 deletions
This file was deleted.

misc/perf-dash/app/mzbuild.yml

Lines changed: 0 additions & 11 deletions
This file was deleted.

0 commit comments

Comments
 (0)