# JMH version: 1.35
# VM version: JDK 1.8.0_152, Java HotSpot(TM) 64-Bit Server VM, 25.152-b16
# VM invoker: **Redacted**
# VM options: **Redacted**
# Blackhole mode: full + dont-inline hint (auto-detected, use -Djmh.blackhole.autoDetect=false to disable)
# Warmup: <none>
# Measurement: 15 iterations, 1 s each
# Timeout: 10 min per iteration
# Threads: 1 thread, will synchronize iterations
# Benchmark mode: Average time, time/op
# Benchmark: com.amazonaws.services.lambda.runtime.api.client.runtimeapi.LambdaRuntimeClientBenchmark.benchmarkPureJavaClient

# Run progress: 0.00% complete, ETA 00:00:15
# Fork: 1 of 1
Iteration   1: 2.239 ms/op
Iteration   2: 0.979 ms/op
Iteration   3: 0.506 ms/op
Iteration   4: 0.471 ms/op
Iteration   5: 0.387 ms/op
Iteration   6: 0.320 ms/op
Iteration   7: 0.300 ms/op
Iteration   8: 0.224 ms/op
Iteration   9: 0.216 ms/op
Iteration  10: 0.211 ms/op
Iteration  11: 0.208 ms/op
Iteration  12: 0.287 ms/op
Iteration  13: 0.210 ms/op
Iteration  14: 0.210 ms/op
Iteration  15: 0.210 ms/op


Result "com.amazonaws.services.lambda.runtime.api.client.runtimeapi.LambdaRuntimeClientBenchmark.benchmarkPureJavaClient":
  0.465 ±(99.9%) 0.567 ms/op [Average]
  (min, avg, max) = (0.208, 0.465, 2.239), stdev = 0.531
  CI (99.9%): [≈ 0, 1.033] (assumes normal distribution)


# Run complete. Total time: 00:00:16

REMEMBER: The numbers below are just data. To gain reusable insights, you need to follow up on
why the numbers are the way they are. Use profilers (see -prof, -lprof), design factorial
experiments, perform baseline and negative tests that provide experimental control, make sure
the benchmarking environment is safe on JVM/OS/HW level, ask for reviews from the domain experts.
Do not assume the numbers tell you what you want them to tell.

Benchmark                                             Mode  Cnt  Score   Error  Units
LambdaRuntimeClientBenchmark.benchmarkPureJavaClient  avgt   15  0.465 ± 0.567  ms/op