https://github.com/alikhachev/gradle-plugin-classloader-benchmark

https://github.com/alikhachev/gradle-plugin-classloader-benchmark

Last synced: 5 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/alikhachev/gradle-plugin-classloader-benchmark
• Owner: ALikhachev
• Created: 2023-02-23T00:21:02.000Z (over 3 years ago)
• Default Branch: main
• Last Pushed: 2023-02-23T00:48:25.000Z (over 3 years ago)
• Last Synced: 2025-09-10T16:07:43.681Z (10 months ago)
• Language: HTML
• Size: 976 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
# Gradle plugin classloader benchmarks

This project contains a synthetic Gradle plugin that loads some API implementation on the flight 

and runs it via Gradle workers API.

It shows difference between two approaches:

1. Using Gradle workers API with classpath isolation. With this approach, Gradle creates a new classloader each time.

2. Using Gradle workers API without isolation. With this approach, we can manage classloaders ourselves and perform its caching

## Results

![Benchmarks results preview](./benchmark-preview.png)

You can find results html [here](./benchmark.html).

They are obtained via [Gradle profiler](https://github.com/gradle/gradle-profiler) running the following command:

`gradle-profiler --measure-gc --scenario-file gradle-profiler.scenarios --benchmark`

**Benchmark environment:**


JDK: Amazon Corretto 17.0.6.10.1


CPU: Apple M1 Max