before:
Started ZipkinServer in 5.258 seconds (JVM running for 6.475)
after:
Started ZipkinServer in 5.028 seconds (JVM running for 6.217)
Trick is that you have to list out the exact paths. this would require us finding them for our "modules" such as scribe, kafka08 and also layered images like zipkin-aws and zipkin-gcp. However, they are in static locations so mostly this is composing env variables I suppose
According to @dsyer, listing config locations can speed up things that otherwise require scanning.
I tried this and it took off a couple hundred ms from the latest image:
before: Started ZipkinServer in 5.258 seconds (JVM running for 6.475)
after: Started ZipkinServer in 5.028 seconds (JVM running for 6.217)
Trick is that you have to list out the exact paths. this would require us finding them for our "modules" such as scribe, kafka08 and also layered images like zipkin-aws and zipkin-gcp. However, they are in static locations so mostly this is composing env variables I suppose
cc @openzipkin/devops-tooling