All Versions
12
Latest Version
Avg Release Cycle
206 days
Latest Release
1126 days ago

Changelog History
Page 1

  • v6.1.0 Changes

    June 13, 2022

    🔄 Changed

  • v6.0.1

    October 21, 2019

  • v6.0.0 Changes

    October 13, 2018

    🔄 Changed

    • 🔄 Change the ETS backend to throw an error if either expiry_ms or cleanup_interval_ms config values are missing. This should have been fixed ages ago.
    • Default :pool_max_overflow changed to 0. It's a better default, given that some users have seen weird errors when using a higher overflow. In general, capacity should be increased by using a higher :pool_size instead
    • 🔄 Changed how the ETS backend does cleanups of data, should be more performant.

  • v5.0.0 Changes

    May 18, 2018

    ➕ Added

    • A new check_rate_inc function, which allows the caller to specify the integer with which to increment the bucket by. This is useful for limiting APIs which have some notion of "cost" per call.

  • v5.0.0-rc1

    May 11, 2018

  • v4.0.0 Changes

    April 23, 2018

    🔄 Changed

    • 👷 Use a worker-pool for the backend (via poolboy), this avoids bottle-necking all traffic through a single hammer process, thus improving throughput for the system overall

    ➕ Added

    • 🆕 New configuration options for backends:
      • :pool_size, determines the number of workers in the pool (default 4)
      • :pool_max_overflow, maximum extra workers to be spawned when the system is under pressure (default 4)
    • Multiple instances of the same backend! You can now have two ETS backends, fifteen Redis's, whatever you want

  • v3.0.0 Changes

    February 20, 2018

    🔄 Changed

    • Require elixir >= 1.6
    • 👉 Use a more sane supervision tree structure

  • v2.1.0 Changes

    November 25, 2017

    🔄 Changed

    • ➕ Add option to use more than one backend
    • ➕ Add option to suppress all logging

  • v2.0.0 Changes

    September 24, 2017

    🔄 Changed

    • 🆕 New, simpler API
      • No longer need to start backend processes manually
      • Call Hammer.check_rate directly, rather than useing a macro
    • 🔧 Hammer is now an OTP application, configured via Mix.Config

  • v1.3.0

    February 20, 2018