https://github.com/pebbletemplates/pebble-performance-test

JMH benchmark of Pebble template engine
https://github.com/pebbletemplates/pebble-performance-test

jmh-benchmarks performance-testing template-engine

Last synced: 23 days ago
JSON representation

JMH benchmark of Pebble template engine

• Host: GitHub
• URL: https://github.com/pebbletemplates/pebble-performance-test
• Owner: PebbleTemplates
• License: bsd-3-clause
• Created: 2018-06-13T01:36:09.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2023-12-05T23:08:17.000Z (about 1 year ago)
• Last Synced: 2024-11-08T20:13:55.225Z (3 months ago)
• Topics: jmh-benchmarks, performance-testing, template-engine
• Language: HTML
• Homepage:
• Size: 18.6 KB
• Stars: 1
• Watchers: 5
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
Running the benchmark [![Build Status](https://travis-ci.org/PebbleTemplates/pebble-performance-test.svg?branch=master)](https://travis-ci.org/PebbleTemplates/pebble-performance-test)

======================

1. Download the source code and build it (`mvn clean package`)

2. Run the entire benchmark suite with `java -jar target/benchmarks.jar`

Generating plot

===============

1. Run benchmark while exporting results to csv with `java -jar target/benchmarks.jar -rff results.csv -rf csv`

2. Use gnuplot to generate plot with `gnuplot benchmark.plot`. This will output `results.png`.

Rules of Template Engine Configuration

======================================

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

Interpreting the Results

========================

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.