Merge pull request #232 from renaissance-benchmarks/release_v0.11.0

Release v0.11.0

.travis.yml

@@ -5,7 +5,7 @@ language: java
 
 env:
  global:
- - RENAISSANCE_VERSION="0.10.0"
+ - RENAISSANCE_VERSION="0.11.0"
 
 refs:
  - &bundle

README.md

@@ -33,7 +33,7 @@ To run a Renaissance benchmark, you need to have a JRE installed.
 This allows you to execute the following `java` command:
 
 ```
-$ java -jar '<renaissance-home>/target/renaissance-gpl-0.10.0.jar' <benchmarks>
+$ java -jar '<renaissance-home>/target/renaissance-gpl-0.11.0.jar' <benchmarks>
 ```
 
 Above, the `<renaissance-home>` is the path to the root directory of the Renaissance distribution,
@@ -58,7 +58,7 @@ policy (see [below](#plugins) for details).
 The following is a complete list of command-line options.
 
 ```
-Renaissance Benchmark Suite, version 0.10.0
+Renaissance Benchmark Suite, version 0.11.0
 Usage: renaissance [options] [benchmark-specification]
 
  -h, --help Prints this usage text.
@@ -296,7 +296,7 @@ $ tools/sbt/bin/sbt renaissanceJmh/jmh:assembly
 To run the benchmarks using JMH, you can execute the following `java` command:
 
 ```
-$ java -jar 'renaissance-jmh/target/scala-2.12/renaissance-jmh-assembly-0.10.0.jar'
+$ java -jar 'renaissance-jmh/target/scala-2.12/renaissance-jmh-assembly-0.11.0.jar'
 ```
 
 

renaissance-core/version.sbt

@@ -1 +1 @@
-version := "0.10.0" // also requires a readme update and a .travis.yml change
+version := "0.11.0" // also requires a readme update and a .travis.yml change

website/_posts/2019-05-06-renaissance-0-9-0.md

@@ -42,4 +42,3 @@ the first major release of the suite which should be ready in few weeks.
 We welcome any comments and contributions.
 
 Happy benchmarking!
-

website/_posts/2019-07-03-renaissance-0-10-0.md

@@ -23,7 +23,7 @@ It helps companies like Oracle, IBM or SAP track performance
 and/or fix bugs. For instance, [this OpenJ9 bug](https://github.com/eclipse/openj9/issues/5726)
 running Apache Spark has been spotted thanks to the Renaissance suite.
 
-We address special thanks to :
+We address special thanks to:
 - [tkrodriguez](https://github.com/tkrodriguez) from Oracle for the in-depth analysis of the `finagle-chirper` bug
 - [vkostyukov](https://github.com/vkostyukov) from Twitter, for his feedback on the Finagle benchmarks
 - [MBaesken](https://github.com/MBaesken) and the SAP Machine team for compatibility testing on less common infrastructures

website/_posts/2020-06-05-renaissance-0-11-0.md

@@ -0,0 +1,31 @@
+---
+layout: mainpost
+projectname: Renaissance Suite
+title: "Renaissance 0.11 Released"
+author: Petr Tuma
+---
+
+A new release of the Renaissance benchmark suite includes several changes to the workloads:
+- `movie-lens` bug fix, where part of the setup was moved out of the core benchmark iteration,
+- `log-regression` bug fix, where input features are cached to avoid parsing the input during each benchmark iteration,
+- `neo4j-analytics` improvement that adds indices and uses placeholder for queries (contributed by Michael Hunger from Neo4J), and
+- `dotty` fix for Windows compatibility.
+
+The Renaissance harness now forces a garbage collection run before each iteration.
+This changes especially the behavior of Spark based workloads, which would otherwise
+retain weakly referenced objects until Spark controlled cleanup once every 30 minutes.
+The garbage collection forced by the harness can be disabled with the `--no-forced-gc` flag.
+
+The harness also includes two plugins,
+`jmx-timers` for collecting the JIT compilation times, and
+`ubench-agent` for collecting the values of arbitrary hardware performance counters.
+
+The JSON result format now also includes OS and system metadata,
+which help capture the benchmark execution conditions across experiments.
+
+We also note that [Renaissance helped tune](https://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2019-December/036332.html) the OpenJDK HotSpot inlining settings.
+
+Special thanks go to:
+- [Michael Hunger](https://github.com/jexp) from Neo4J for his contribution on the `neo4j-analytics` benchmark,
+- [Guillaumes Martres](https://github.com/smarter) from EPFL for his input on fixing the `dotty` benchmark for Windows, and
+- [Tom Rodriguez](https://github.com/tkrodriguez) from Oracle Labs for spotting a bug in `log-regression`.