Skip to content
Snippets Groups Projects
Commit 94068153 authored by Sören Henning's avatar Sören Henning
Browse files

Improve benchmarks readme

parent 409d2f14
No related branches found
No related tags found
No related merge requests found
Pipeline #10370 passed
...@@ -4,6 +4,16 @@ Theodolite comes with a set of 4 benchmarks for event-driven microservices, whic ...@@ -4,6 +4,16 @@ Theodolite comes with a set of 4 benchmarks for event-driven microservices, whic
The benchmarks are based on typical use cases for stream processing and named: UC1, UC2, UC3 and UC4. The benchmarks are based on typical use cases for stream processing and named: UC1, UC2, UC3 and UC4.
Additionally, we include a load generator for each benchmark. Additionally, we include a load generator for each benchmark.
## Project organization
All benchmark implementations are organized in a Gradle multi-project. See the [`settings.gradle`](settings.gradle) file for an overview of subprojects and how they are organized.
We also use Gradle convention plugins, organized in [`buildSrc`](buildSrc), for sharing build configuration among subprojects.
Additionally, this directory contains:
* *Theodolite* Benchmark definitions for all benchmarks in [`definitions`](definitions).
* Docker Compose files to assist in local development and to run smoke tests in [`docker-test`](docker-test).
## Building and packaging the benchmarks ## Building and packaging the benchmarks
All benchmarks can be built with: All benchmarks can be built with:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment