Commit 1b5ce13
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- bin
- ci/test
- doc/developer
- misc/perf-dash
- app
- templates
- create_views
- views
- scraper
- metrics
- dev.mtrlz.time_per_operator.v0
- dev.mtrlz.time_per_operator_per_worker.v0
- dev.mtrlz.time_per_worker.v0
- test/bench
- aggregations
- create_views
- views
- generator
- distributions
- benchmark
- medium
- small
- prometheus
- avro-insert
- create_views
- views
- prometheus
- avro-upsert
- create_views
- views
- prometheus
- kafka-sink-avro-debezium
- create_sink
- sinks
- prometheus
- util
- kafka-avro-generator
- distributions
- benchmark
- big-records
- medium
- small
- metric-verifier
- schemas
- dev.mtrlz.benchmarks.runs.begin.v0
- dev.mtrlz.benchmarks.runs.params.v0
- dev.mtrlz.benchmarks.runs.results.v0
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 changedThis file was deleted.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
186 | 186 | | |
187 | 187 | | |
188 | 188 | | |
189 | | - | |
190 | | - | |
191 | | - | |
192 | | - | |
193 | | - | |
194 | | - | |
195 | | - | |
196 | | - | |
197 | | - | |
198 | | - | |
199 | | - | |
200 | | - | |
201 | | - | |
202 | | - | |
203 | | - | |
204 | | - | |
205 | | - | |
206 | | - | |
207 | | - | |
208 | | - | |
209 | | - | |
210 | | - | |
211 | | - | |
212 | | - | |
213 | | - | |
214 | | - | |
215 | | - | |
216 | 189 | | |
217 | 190 | | |
218 | 191 | | |
| |||
This file was deleted.
This file was deleted.
This file was deleted.
0 commit comments