Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add micro-benchmarks to JMH #159

Merged
merged 4 commits into from May 14, 2016
Merged

Add micro-benchmarks to JMH #159

merged 4 commits into from May 14, 2016

Conversation

ryangardner
Copy link
Member

There is a README.md file that describes how to execute these benchmarks.

I don't have then running automatically as part of the build because they take some time to run - a few minutes each one.

You can either package them up and run them all at once or you can run them individually in an IDE. Running them individually in an IDE is pretty cool because in your IDE (at least in IntelliJ) you can open the togglz project, make changes to something, and then run just the one benchmark you are interested in to see if your new tweaks made things any better or not.

I added a baseline one that compares the performance of the togglz vs a boolean if flag, another one that looks at how it performs when you use an activation strategy, and another one that tests how it performs when you use a ScriptEngine.

Create a module with runnable jmh-benchmarks for the togglz project with a simple benchmark that compares the overhead of the togglz library vs a simple boolean.
@chkal chkal merged commit 1f735f1 into togglz:master May 14, 2016
@chkal
Copy link
Member

chkal commented May 14, 2016

Awesome! Thank you soooo much for contributing this.

Just a side note. I think I'll rename the module from togglz-benchmarks to simply benchmarks in the next days as this fits better to the naming scheme of the other modules. Even so it is some kind of "special" module. ;)

Again: Thanks so much for this...

@ryangardner ryangardner deleted the benchmarks branch June 2, 2016 19:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants