# JMH version: 1.21
# VM version: JDK 1.8.0_121, Java HotSpot(TM) 64-Bit Server VM, 25.121-b13
# VM invoker: /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/bin/java
# VM options: -Didea.launcher.port=7538 -Didea.launcher.bin.path=/Applications/IntelliJ IDEA.app/Contents/bin -Dfile.encoding=UTF-8
# Warmup: 1 iterations, 10 s each
# Measurement: 3 iterations, 10 s each
# Timeout: 10 min per iteration
# Threads: 10 threads, will synchronize iterations
# Benchmark mode: Throughput, ops/time
# Benchmark: redis.YaliRedis.test
# Run progress: 0.00% complete, ETA 00:00:40
# Fork: 1 of 1
# Warmup Iteration 1: me
me
me
me
me
me
me
me
me
me
38157.549 ops/s
Iteration 1: 40937.006 ops/s
Iteration 2: 40624.199 ops/s
Iteration 3: 35236.725 ops/s
Result "redis.YaliRedis.test":
38932.643 ±(99.9%) 58463.439 ops/s [Average]
(min, avg, max) = (35236.725, 38932.643, 40937.006), stdev = 3204.578
CI (99.9%): [≈ 0, 97396.082] (assumes normal distribution)
# Run complete. Total time: 00:00:41
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
YaliRedis.test thrpt 3 38932.643 ± 58463.439 ops/s
Process finished with exit code 0