Build(deps-dev): Bump benchee from 1.0.1 to 1.1.0

[dependabot]

Bumps benchee from 1.0.1 to 1.1.0.

Release notes

Sourced from benchee's releases.

1.1.0

Long time, huh? I'm sorry, combination of priorities, difficult to fix bugs, stress and arm problems kept me away too long. This release brings major features long developed and now finally released (reduction measurements + profiler after run), along with a critical bugfix around measurement accuracy for very fast functions (nanoseconds).

Features (User Facing)

• Reduction counting/measurements was implemented. Basically, it's a rather stable unit of execution implemented by the BEAM that measures in more abstract manner how much work was done. It's helpful, as it shouldn't be affected by load on the system. Check out the docs.
• You can now dive straight into profiling from your benchmarks by using the profiling feature. See the docs - thanks @​pablocostass

Default Behavior Changes (User Facing)

• measuring function call overhead is now turned off by default, as it only helps with extreme nano benchmarks and has some potential for causing wrong results, so it should only be opt in. We now also print out the measured overhead for vsibility.

Bugfixes (User Facing)

• Benchee now correctly looks for the time resolution as reported by :erlang.system_info(:os_monotonic_time_source) to accomodate when determining if a measurement is "precise" enough. Benche also works around an erlang bug we discovered present in erlang <= 22.2. Issue for reference.
• The annoying stacktrace warning has been removed - thanks @​mad42

Noteworthy

• a new dependency statistex will show up - it's a part of continued efforts to extract reusable libraries from Benchee.

Changelog

Sourced from benchee's changelog.

1.1.0 (2022-03-08)

Long time, huh? I'm sorry, combination of priorities, difficult to fix bugs, stress and arm problems kept me away too long. This release brings major features long developed and now finally released (reduction measurements + profiler after run), along with a critical bugfix around measurement accuracy for very fast functions (nanoseconds).

Features (User Facing)

• Reduction counting/measurements was implemented. Basically, it's a rather stable unit of execution implemented by the BEAM that measures in more abstract manner how much work was done. It's helpful, as it shouldn't be affected by load on the system. Check out the docs.
• You can now dive straight into profiling from your benchmarks by using the profiling feature. See the docs - thanks @​pablocostass

Default Behavior Changes (User Facing)

• measuring function call overhead is now turned off by default, as it only helps with extreme nano benchmarks and has some potential for causing wrong results, so it should only be opt in. We now also print out the measured overhead for vsibility.

Bugfixes (User Facing)

• Benchee now correctly looks for the time resolution as reported by :erlang.system_info(:os_monotonic_time_source) to accomodate when determining if a measurement is "precise" enough. Benche also works around an erlang bug we discovered present in erlang <= 22.2. Issue for reference.
• The annoying stacktrace warning has been removed - thanks @​mad42

Noteworthy

• a new dependency statistex will show up - it's a part of continued efforts to extract reusable libraries from Benchee.

Commits

• 2547b54 Move dialyzer plt files around
• ce5577c Last pass on Changelog for 1.1.0, hopefully
• 7176729 more fun with retrying profiler tests
• ee84286 Doc some internal modules to avoid hexdoc warnings
• 4403189 Woopsie forgot to use test times and ballooned test run time
• fd65468 Avoid random failures in this test for whatever reason
• 628beec Replace all mentions of master with main
• fa67b57 Replace all old schoo mentions of PragTob/benchee with bencheeorg
• 3508ab3 Table of contents
• 59ef73f Better changelog linking to docs
• Additional commits viewable in compare view

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 squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor 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)