* Skeleton for overhead testing subproject. * clone into base image instead of submodule * remove submodules file (even though it was empty) * set up a junit-based test running project that leverages testcontianers. * remove builder * remove builder * cleanup * repackage * update base image url * leverage an agent object * add optional jvmargs to the Agent * cleanup and handle file urls * allow overwrite * cleanup * simplify writing * simplify writing * remove dead comment * pass url |
||
---|---|---|
.. | ||
gradle/wrapper | ||
k6 | ||
src/test | ||
.dockerignore | ||
Dockerfile-petclinic-base | ||
README.md | ||
build.gradle.kts | ||
gradlew | ||
settings.gradle.kts |
README.md
Overhead tests
This is a work in progress.
This directory will contain tools and utilities that help us to measure the performance overhead introduced by the agent and to measure how this overhead changes over time.
Contents
tbd
Config
tbd
Setup and Usage
Once we have an established base image published for spring-petclinic-rest
, this step
can be avoided by most users. For now, there is just a spring petclinic base image.
$ docker build -f Dockerfile-petclinic-base .
Remaining usage TBD.