personally, wanted to have JMH available as a test dependency a few times already :)
but than I usually just went with micro benchmarking Ruby directly. not sure if all are worth converting, maybe a few - some new benchmarks might be interesting (e.g. not really sure about the intern-ing you did)

@kares nice :)

some new benchmarks might be interesting (e.g. not really sure about the intern-ing you did)

Exactly! This would make demonstrating/evaluating improvements much easier :)

That said, let's do it! (this should be fairly quick and trivial:)) Where should we put the Maven module for this? Just top level jmh-bench/pom.xml maybe?

not sure if we would need a new 'module' ... maybe some of the existing places can be (re-)used :

1. have JMH available as a test dependency on core and write bms under org.jruby.bench
   ... although I am not sure if that would make much sense -> they won't be run during tests anyway
2. bench directory contains .rb (micro) benchmarks - that might be converted to a maven module
   ... having src/main/java for JMH and src/main/ruby for Ruby-style benchmarks

JRuby usually uses pom.rb but that shouldn't matter a raw pom.xml will be just fine, since it will be an isolated module anyway. might be some build tricks needed to keep it up-to-date - could be solved later.

@kares let's do 2. :) JMH tests should be an isolated module that depends on whatever module you want to benchmark ideally.
Quote from http://openjdk.java.net/projects/code-tools/jmh/

The recommended way to run a JMH benchmark is to use Maven to setup a standalone project that depends on the jar files of your application. This approach is preferred to ensure that the benchmarks are correctly initialized and produce reliable results. It is possible to run benchmarks from within an existing project, and even from within an IDE, however setup is more complex and the results are less reliable.

This is how I set it up for Logstash https://github.com/elastic/logstash/tree/master/logstash-core/benchmarks and I think we could do the same by putting some pom.rb under /bench right? Could even add a comfortable Maven build target for it like I did in LS for rebuild + running those JMH benchmarks in a single step :)

@kares port the other two benchmarks in that package to JMH as well? :)

@original-brownbear if you're into that I do not see why not ... should be useful as an inspiration at least

@kares sure it was a really small effort left anyways :) + looks so much nicer now imo.
Check out #4774 if you have a sec :)