# java-benchmarks

**Repository Path**: mirrors_opentracing-contrib/java-benchmarks

## Basic Information

- **Project Name**: java-benchmarks
- **Description**: Set of benchmarks to assess the performance of different OpenTracing components and/or libraries
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2020-08-18
- **Last Updated**: 2026-02-28

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# JMH benchmark for OpenTracing libraries

This repository contains a set of benchmarks to assess the performance of different OpenTracing components and/or libraries. Some tests might include concrete implementations, such as Jaeger and Haystack, mostly for sanity checking purposes.

List of current tests:

| Test                                            | No Instrumentation | Noop Tracer | Mock Tracer | Jaeger Tracer | Haystack Tracer |
| ----------------------------------------------- | ------------------ | ----------- | ----------- | ------------- | --------------- |
| Throughput, one span, one tag, one log message  |          ✓         |      ✓      |       ✓     |       ✓       |        ✓        |
| Time, one span, one tag, one log message        |          ✓         |      ✓      |       ✓     |       ✓       |        ✓        |

## Code structure

Each benchmark contains common packages to the same purpose: 

```
opentracing-benchmark-spring-cloud
│   
│   
└───io.opentracing.contrib.benchmarks
│   │
│   └───config
│   │   ## Classes to initialize the different tracers
│   │
│   └───main
│   │   ## The class to be executed by JMH 
│   │
│   └───petclinic
│   │   ## Depending on the test, there is one package which contains the example application to be executed by JMH. 
│   │      In this example for opentracing for spring cloud, the official petclinic application is used for the tests.
│   │    
│   Benchmark*.java 
│   ## The different JMH benchmark tests are located in this package
│   │
```

And depending on the project there are some specific packages, like `listeners` or `servlets`, etc. 

## Properties

This properties can be overrided by system properties:

```properties
benchmark.warmup.iterations=5
benchmark.test.iterations=5
benchmark.test.forks=1
benchmark.test.threads=1
benchmark.global.testclassregexpattern=.*Benchmark.*
benchmark.global.resultfileprefix=jmh-

```

## Running it
Run the following command (inside on a specific project)

```
mvn clean install
java -jar target/benchmarks.jar
```

## Feedback

Performance tests are tricky and we are sure that some things might have done better. We welcome your constructive comments and we appreciate PRs.

## Results
We use [JMH-visualizer](https://github.com/jzillmann/jmh-visualizer) to present the benchmark results. Thanks [jzillmann](https://github.com/jzillmann) 
for this amazing tool!. 

The results of different scenarios are located in each project:
- [opentracing-benchmark-simple-java](https://github.com/opentracing-contrib/java-benchmarks/tree/master/opentracing-benchmark-simple-java)
- [opentracing-benchmark-spring-boot](https://github.com/opentracing-contrib/java-benchmarks/tree/master/opentracing-benchmark-spring-boot)
- [opentracing-benchmark-java-servlet-filter](https://github.com/opentracing-contrib/java-benchmarks/tree/master/opentracing-benchmark-java-servlet-filter)
- [opentracing-benchmark-spring-cloud](https://github.com/opentracing-contrib/java-benchmarks/tree/master/opentracing-benchmark-spring-cloud)
- [opentracing-benchmark-java-jaxrs](https://github.com/opentracing-contrib/java-benchmarks/tree/master/opentracing-benchmark-java-jaxrs)
- [opentracing-benchmark-java-jdbc](https://github.com/opentracing-contrib/java-benchmarks/tree/master/opentracing-benchmark-java-jdbc)