JMH benchmark for popular Java template engines:

• Meepo
• Freemarker
• Mustache
• Pebble
• Rocker
• Thymeleaf
• Trimou
• Velocity

Result "com.mitchellbosecke.benchmark.Velocity.benchmark":
  18956.594 ±(99.9%) 766.578 ops/s [Average]
  (min, avg, max) = (12635.749, 18956.594, 20754.686), stdev = 1548.525
  CI (99.9%): [18190.016, 19723.172] (assumes normal distribution)
# Run complete. Total time: 01:27:47

1. Download the source code and build it (mvn clean install)
2. Run the entire benchmark suite with java -jar target/benchmarks.jar
3. (Optional) To run a single benchmark, such as Mustache, use java -jar target/benchmarks.jar Mustache

1. Run benchmark while exporting results to csv with java -jar target/benchmarks.jar -f 1 -rff results.csv -rf csv
2. Use gnuplot to generate plot with gnuplot benchmark.plot. This will output results.png.
3. Use jfr java -jar target/benchmarks.jar Meepo -f 1 -prof jfr
4. use jmc to analyse the profile.jfr

It is imperative that each template engine is configured in way to reflect real-world usage as opposed to it's optimal configuration. Typically this means an out-of-the-box configuration.

To strive for a common set of features across template engines, the following configurations are expected:

• Disabling of HTML escaping
• Template loaded from classpath prior to actual benchmark

The benchmarks measure throughput, given in "ops/time". The time unit used is seconds. Generally, the score represents the number of templates rendered per second; the higher the score, the better.