michaelherold / benchmark-memory

Memory profiling benchmark style, for Ruby 2.1+
MIT License
217 stars 6 forks source link

Allow for sorting by different criteria #23

Closed michaelherold closed 2 years ago

michaelherold commented 2 years ago

Sometimes, you want to compare retained memory instead of allocated memory. This is useful when you want to check for a memory leak in different implementations of an algorithm. This change introduces the ability to compare the retained memory of your benchmarks.

This also includes a CI fix and a development harness fix. First, it ensures that Bundler is installed in the CI environment. Second, it checks the Gemfile.lock file into the repository to make it easier for CI and new contributors.