Release notes
*Sourced from [benchee's releases](https://github.com/PragTob/benchee/releases).*
> ## 0.14.0
> ### Breaking Changes (User Facing)
> * dropped support for Erlang 18.x
> * Formatters no longer have an `output/1` method, instead use `Formatter.output/3` please
> * Usage of `formatter_options` is deprecated, instead please use the new tuple way
>
> ### Features (User Facing)
> * benchee now uses the maximum precision available to measure which on Linux and OSX is nanoseonds instead of microseconds. Somewhat surprisingly `:timer.tc/1` always cut down to microseconds although better precision is available.
> * The preferred way to specify formatters and their options is to specify them as a tuple `{module, options}` instead of using `formatter_options`.
> * New `Formatter.output/1` function that takes a suite and uses all configured formatters to output their results
> * Add the concept of a benchmarking title that formatters can pick up
> * the displayed percentiles can now be adjusted
> * inputs option can now be an ordered list of tuples, this way you can determine their order
> * support FreeBSD properly (system metrics) - thanks @[kimshrier](https://github.com/PragTob/benchee/blob/HEAD/kimshrier)
>
> ### Bugfixes (User Facing)
> * Remove extra double quotes in operating system report line - thanks @[kimshrier](https://github.com/PragTob/benchee/blob/HEAD/kimshrier)
>
> ### Breaking Changes (Plugins)
> * all reported times are now in nanoseconds instead of microseconds
> * formatter methods `format` and `write` now take 2 arguments each where the additional arguments is the options specified for this formatter so that you have direct access to it without peeling it from the suite
> * You can no longer `use Benchee.Formatter` - just adopt the behaviour (no more auto generated `output/1` method, but `Formatter.output/3` takes that responsibility now)
>
> ### Features (Plugins)
> * An optional title is now available in the suite for you to display
> * Scenarios are now sorted already sorted (first by run time, then memory usage) - no need to sort them yourself!
> * Add `Scenario.data_processed?/2` to check if either run time or memory data has had statistics generated
Changelog
*Sourced from [benchee's changelog](https://github.com/PragTob/benchee/blob/master/CHANGELOG.md).*
> ## 0.14.0 (2019-02-10)
>
> ### Breaking Changes (User Facing)
> * dropped support for Erlang 18.x
> * Formatters no longer have an `output/1` method, instead use `Formatter.output/3` please
> * Usage of `formatter_options` is deprecated, instead please use the new tuple way
>
> ### Features (User Facing)
> * benchee now uses the maximum precision available to measure which on Linux and OSX is nanoseonds instead of microseconds. Somewhat surprisingly `:timer.tc/1` always cut down to microseconds although better precision is available.
> * The preferred way to specify formatters and their options is to specify them as a tuple `{module, options}` instead of using `formatter_options`.
> * New `Formatter.output/1` function that takes a suite and uses all configured formatters to output their results
> * Add the concept of a benchmarking title that formatters can pick up
> * the displayed percentiles can now be adjusted
> * inputs option can now be an ordered list of tuples, this way you can determine their order
> * support FreeBSD properly (system metrics) - thanks @[kimshrier](https://github.com/PragTob/benchee/blob/master/kimshrier)
>
> ### Bugfixes (User Facing)
> * Remove extra double quotes in operating system report line - thanks @[kimshrier](https://github.com/PragTob/benchee/blob/master/kimshrier)
>
> ### Breaking Changes (Plugins)
> * all reported times are now in nanoseconds instead of microseconds
> * formatter methods `format` and `write` now take 2 arguments each where the additional arguments is the options specified for this formatter so that you have direct access to it without peeling it from the suite
> * You can no longer `use Benchee.Formatter` - just adopt the behaviour (no more auto generated `output/1` method, but `Formatter.output/3` takes that responsibility now)
>
> ### Features (Plugins)
> * An optional title is now available in the suite for you to display
> * Scenarios are now sorted already sorted (first by run time, then memory usage) - no need to sort them yourself!
> * Add `Scenario.data_processed?/2` to check if either run time or memory data has had statistics generated
Commits
- [`fbffd52`](https://github.com/PragTob/benchee/commit/fbffd52ebf1c1ed7ecfe51ae7be001fd6d0aa6c8) 0.14.0
- [`2af85e4`](https://github.com/PragTob/benchee/commit/2af85e43aa87f4c0178d4326e025658c07d4f668) formatting fix for docs
- [`8504fca`](https://github.com/PragTob/benchee/commit/8504fca85604d282a947dc9adde0e44ed2e89b24) formatted sample
- [`b6ec8be`](https://github.com/PragTob/benchee/commit/b6ec8be2fae73eced2501866c9c79b066de1c1c6) updates ([#269](https://github-redirect.dependabot.com/PragTob/benchee/issues/269))
- [`7216d6d`](https://github.com/PragTob/benchee/commit/7216d6da0ffb24dbb48235789e339a0cdb39606b) Merge pull request [#267](https://github-redirect.dependabot.com/PragTob/benchee/issues/267) from PragTob/changelog-update
- [`2fd7094`](https://github.com/PragTob/benchee/commit/2fd70943a9c572bd563cdf59b7b9492c3e815f15) `Scenario.data_processed?/2` entry
- [`0261693`](https://github.com/PragTob/benchee/commit/02616939306fb0abcccb2bbdf28fd02d5faf138f) Add Scenario.data_processed? to simplify checks in formatters ([#268](https://github-redirect.dependabot.com/PragTob/benchee/issues/268))
- [`d6c3af8`](https://github.com/PragTob/benchee/commit/d6c3af8d3addf3a8fad3c17a92969344bde2df74) Catch up on changelog entries
- [`a295b4f`](https://github.com/PragTob/benchee/commit/a295b4fd538c1d1b204f2f565daff94fcd53558c) Merge pull request [#265](https://github-redirect.dependabot.com/PragTob/benchee/issues/265) from kimshrier/system_freebsd
- [`d4dc357`](https://github.com/PragTob/benchee/commit/d4dc357f2be0a70a19c8a1eac7b5346ccd100577) Merge pull request [#266](https://github-redirect.dependabot.com/PragTob/benchee/issues/266) from kimshrier/report_typo
- Additional commits viewable in [compare view](https://github.com/PragTob/benchee/compare/0.13.2...0.14.0)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Bumps benchee from 0.13.2 to 0.14.0.
Release notes
*Sourced from [benchee's releases](https://github.com/PragTob/benchee/releases).* > ## 0.14.0 > ### Breaking Changes (User Facing) > * dropped support for Erlang 18.x > * Formatters no longer have an `output/1` method, instead use `Formatter.output/3` please > * Usage of `formatter_options` is deprecated, instead please use the new tuple way > > ### Features (User Facing) > * benchee now uses the maximum precision available to measure which on Linux and OSX is nanoseonds instead of microseconds. Somewhat surprisingly `:timer.tc/1` always cut down to microseconds although better precision is available. > * The preferred way to specify formatters and their options is to specify them as a tuple `{module, options}` instead of using `formatter_options`. > * New `Formatter.output/1` function that takes a suite and uses all configured formatters to output their results > * Add the concept of a benchmarking title that formatters can pick up > * the displayed percentiles can now be adjusted > * inputs option can now be an ordered list of tuples, this way you can determine their order > * support FreeBSD properly (system metrics) - thanks @[kimshrier](https://github.com/PragTob/benchee/blob/HEAD/kimshrier) > > ### Bugfixes (User Facing) > * Remove extra double quotes in operating system report line - thanks @[kimshrier](https://github.com/PragTob/benchee/blob/HEAD/kimshrier) > > ### Breaking Changes (Plugins) > * all reported times are now in nanoseconds instead of microseconds > * formatter methods `format` and `write` now take 2 arguments each where the additional arguments is the options specified for this formatter so that you have direct access to it without peeling it from the suite > * You can no longer `use Benchee.Formatter` - just adopt the behaviour (no more auto generated `output/1` method, but `Formatter.output/3` takes that responsibility now) > > ### Features (Plugins) > * An optional title is now available in the suite for you to display > * Scenarios are now sorted already sorted (first by run time, then memory usage) - no need to sort them yourself! > * Add `Scenario.data_processed?/2` to check if either run time or memory data has had statistics generatedChangelog
*Sourced from [benchee's changelog](https://github.com/PragTob/benchee/blob/master/CHANGELOG.md).* > ## 0.14.0 (2019-02-10) > > ### Breaking Changes (User Facing) > * dropped support for Erlang 18.x > * Formatters no longer have an `output/1` method, instead use `Formatter.output/3` please > * Usage of `formatter_options` is deprecated, instead please use the new tuple way > > ### Features (User Facing) > * benchee now uses the maximum precision available to measure which on Linux and OSX is nanoseonds instead of microseconds. Somewhat surprisingly `:timer.tc/1` always cut down to microseconds although better precision is available. > * The preferred way to specify formatters and their options is to specify them as a tuple `{module, options}` instead of using `formatter_options`. > * New `Formatter.output/1` function that takes a suite and uses all configured formatters to output their results > * Add the concept of a benchmarking title that formatters can pick up > * the displayed percentiles can now be adjusted > * inputs option can now be an ordered list of tuples, this way you can determine their order > * support FreeBSD properly (system metrics) - thanks @[kimshrier](https://github.com/PragTob/benchee/blob/master/kimshrier) > > ### Bugfixes (User Facing) > * Remove extra double quotes in operating system report line - thanks @[kimshrier](https://github.com/PragTob/benchee/blob/master/kimshrier) > > ### Breaking Changes (Plugins) > * all reported times are now in nanoseconds instead of microseconds > * formatter methods `format` and `write` now take 2 arguments each where the additional arguments is the options specified for this formatter so that you have direct access to it without peeling it from the suite > * You can no longer `use Benchee.Formatter` - just adopt the behaviour (no more auto generated `output/1` method, but `Formatter.output/3` takes that responsibility now) > > ### Features (Plugins) > * An optional title is now available in the suite for you to display > * Scenarios are now sorted already sorted (first by run time, then memory usage) - no need to sort them yourself! > * Add `Scenario.data_processed?/2` to check if either run time or memory data has had statistics generatedCommits
- [`fbffd52`](https://github.com/PragTob/benchee/commit/fbffd52ebf1c1ed7ecfe51ae7be001fd6d0aa6c8) 0.14.0 - [`2af85e4`](https://github.com/PragTob/benchee/commit/2af85e43aa87f4c0178d4326e025658c07d4f668) formatting fix for docs - [`8504fca`](https://github.com/PragTob/benchee/commit/8504fca85604d282a947dc9adde0e44ed2e89b24) formatted sample - [`b6ec8be`](https://github.com/PragTob/benchee/commit/b6ec8be2fae73eced2501866c9c79b066de1c1c6) updates ([#269](https://github-redirect.dependabot.com/PragTob/benchee/issues/269)) - [`7216d6d`](https://github.com/PragTob/benchee/commit/7216d6da0ffb24dbb48235789e339a0cdb39606b) Merge pull request [#267](https://github-redirect.dependabot.com/PragTob/benchee/issues/267) from PragTob/changelog-update - [`2fd7094`](https://github.com/PragTob/benchee/commit/2fd70943a9c572bd563cdf59b7b9492c3e815f15) `Scenario.data_processed?/2` entry - [`0261693`](https://github.com/PragTob/benchee/commit/02616939306fb0abcccb2bbdf28fd02d5faf138f) Add Scenario.data_processed? to simplify checks in formatters ([#268](https://github-redirect.dependabot.com/PragTob/benchee/issues/268)) - [`d6c3af8`](https://github.com/PragTob/benchee/commit/d6c3af8d3addf3a8fad3c17a92969344bde2df74) Catch up on changelog entries - [`a295b4f`](https://github.com/PragTob/benchee/commit/a295b4fd538c1d1b204f2f565daff94fcd53558c) Merge pull request [#265](https://github-redirect.dependabot.com/PragTob/benchee/issues/265) from kimshrier/system_freebsd - [`d4dc357`](https://github.com/PragTob/benchee/commit/d4dc357f2be0a70a19c8a1eac7b5346ccd100577) Merge pull request [#266](https://github-redirect.dependabot.com/PragTob/benchee/issues/266) from kimshrier/report_typo - Additional commits viewable in [compare view](https://github.com/PragTob/benchee/compare/0.13.2...0.14.0)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.