MemoWise

Why MemoWise?

MemoWise is the wise choice for Ruby memoization, featuring:

• Fast performance of memoized reads (with benchmarks)
• Support for resetting and presetting memoized values
• Support for memoization on frozen objects
• Support for memoization of class and module methods
• Support for inheritance of memoized class and instance methods
• Documented and tested thread-safety guarantees
• Full documentation and test coverage!

Installation

Add this line to your application's Gemfile:

gem 'memo_wise'

And then execute:

$ bundle install

Or install it yourself as:

$ gem install memo_wise

Usage

When you prepend MemoWise within a class or module, MemoWise exposes three methods:

• memo_wise
• preset_memo_wise
• reset_memo_wise

class Example
  prepend MemoWise

  def slow_value(x)
    sleep x
    x
  end
  memo_wise :slow_value

  private

  # maintains privacy of the memoized method
  def private_slow_method(x)
    sleep x
    x
  end
  memo_wise :private_slow_method
end

ex = Example.new
ex.slow_value(2) # => 2 # Sleeps for 2 seconds before returning
ex.slow_value(2) # => 2 # Returns immediately because the result is memoized

ex.reset_memo_wise(:slow_value) # Resets all memoized results for slow_value
ex.slow_value(2) # => 2 # Sleeps for 2 seconds before returning
ex.slow_value(2) # => 2 # Returns immediately because the result is memoized
# NOTE: Memoization can also be reset for all methods, or for just one argument.

ex.preset_memo_wise(:slow_value, 3) { 4 } # Store 4 as the result for slow_value(3)
ex.slow_value(3) # => 4 # Returns immediately because the result is memoized
ex.reset_memo_wise # Resets all memoized results for all methods on ex

The same three methods are exposed for class methods as well:

class Example
  prepend MemoWise

  def self.class_slow_value(x)
    sleep x
    x
  end
  memo_wise self: :class_slow_value
end

Example.class_slow_value(2) # => 2 # Sleeps for 2 seconds before returning
Example.class_slow_value(2) # => 2 # Returns immediately because the result is memoized

Example.reset_memo_wise(:class_slow_value) # Resets all memoized results for class_slow_value

Example.preset_memo_wise(:class_slow_value, 3) { 4 } # Store 4 as the result for slow_value(3)
Example.class_slow_value(3) # => 4 # Returns immediately because the result is memoized
Example.reset_memo_wise # Resets all memoized results for all methods on class

NOTE: Methods which take implicit or explicit block arguments cannot be memoized.

For more usage details, see our detailed documentation.

Benchmarks

Benchmarks are run in GitHub Actions, and the tables below are updated with every code change. Values >1.00x represent how much slower each gem’s memoized value retrieval is than the latest commit of MemoWise, according to benchmark-ips (2.14.0).

Results using Ruby 3.3.5:

Method arguments	alt_memery (2.1.0)	dry-core* (1.0.1)	memery (1.6.0)	memoist3 (1.0.0)
() (none)	11.84x	0.67x	3.10x	2.58x
(a)	9.50x	1.11x	3.78x	15.21x
(a, b)	7.67x	0.93x	3.00x	12.06x
(a:)	15.99x	1.16x	7.12x	21.32x
(a:, b:)	12.83x	0.91x	5.70x	21.20x
(a, b:)	12.95x	0.94x	5.72x	17.11x
(a, *args)	1.89x	0.70x	0.74x	2.91x
(a:, **kwargs)	2.81x	0.69x	1.19x	4.65x
(a, *args, b:, **kwargs)	1.66x	0.58x	0.81x	2.80x

* dry-core may cause incorrect behavior caused by hash collisions.

Results using Ruby 2.7.8 (because these gems raise errors in Ruby 3.x):

Method arguments	ddmemoize (1.0.0)	memoist (0.16.2)	memoized (1.1.1)	memoizer (1.0.3)
() (none)	24.14x	2.44x	23.84x	2.59x
(a)	22.16x	14.80x	20.70x	11.67x
(a, b)	19.39x	13.66x	18.03x	11.46x
(a:)	30.54x	23.68x	25.21x	21.20x
(a:, b:)	27.75x	22.59x	23.47x	20.65x
(a, b:)	26.72x	21.39x	21.73x	19.43x
(a, *args)	3.26x	2.31x	3.09x	1.93x
(a:, **kwargs)	2.87x	2.29x	2.51x	2.10x
(a, *args, b:, **kwargs)	2.23x	1.88x	1.97x	1.73x

You can run benchmarks yourself with:

$ cd benchmarks
$ bundle install
$ bundle exec ruby benchmarks.rb

If your results differ from what's posted here, let us know!

Thread Safety

MemoWise makes the following thread safety guarantees on all supported Ruby versions:

1. Before a value has been memoized

   • Contended calls from multiple threads...
     • May each call the original method
     • May return different valid results (when the method is nondeterministic, like rand)
     • Will memoize exactly one valid return value

2. After a value has been memoized

   • Contended calls from multiple threads...
     • Always return the same memoized value

Documentation

Automatically Generated Docs

We maintain API documentation using YARD, which is published automatically at RubyDoc.info.

To generate documentation locally or run documentation tests, first install the docs dependencies (e.g. yard) as follows:

BUNDLE_WITH=docs bundle install

Hot Reloading Docs Locally

To edit documentation locally and see it rendered in your browser using hot reloading, run:

bundle exec yard server --reload

You can then open your web browser to http://127.0.0.1:8808/. As you edit documentation locally, reload your browser to see it generated.

Static Generate Docs Locally

To statically generate documentation locally, run:

bundle exec yard

You can then open the generated documentation at docs/index.html.

Test all Docs Examples

We use yard-doctest to test all code examples in our YARD documentation. To run doctest locally:

bundle exec yard doctest

We use dokaz to test all code examples in this README.md file, and all other non-code documentation. To run dokaz locally:

bundle exec dokaz

A Note on Testing

When testing memoized module methods, note that some testing setups will reuse the same instance (which includes/extends/prepends the module) across tests, which can result in confusing test failures when this differs from how you use the code in production.

For example, Rails view helpers are modules that are commonly tested with a shared view instance. Rails initializes a new view instance for each web request so any view helper methods would only be memoized for the duration of that web request, but in tests (such as when using rspec-rails's helper), the memoization may persist across tests. In this case, simply reset the memoization between your tests with something like:

after(:each) { helper.reset_memo_wise }

Further Reading

We presented at RubyConf 2021:

• Achieving Fast Method Metaprogramming: Lessons from MemoWise (slides / benchmarks)

And we've written more about MemoWise in a series of blog posts:

• Introducing: MemoWise
• Optimizing MemoWise Performance
• Esoteric Ruby in MemoWise

Logo

MemoWise's logo was created by Luci Cooke. The logo is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/panorama-ed/memo_wise. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

Releasing

To make a new release of MemoWise to RubyGems, first install the release dependencies (e.g. rake) as follows:

BUNDLE_WITH=release bundle install

Then carry out these steps:

1. Update CHANGELOG.md:

   • Add an entry for the upcoming version x.y.z
   • Move content from Unreleased to the upcoming version x.y.z
   • Update the diff links for this version and Unreleased in CHANGELOG.md
   • Change Unreleased section to say:

     **Gem enhancements:** none
     
     _No breaking changes!_
     
     **Project enhancements:** none
     

   • Commit with title Update CHANGELOG.md for x.y.z

2. Update lib/memo_wise/version.rb

   • Replace with upcoming version x.y.z
   • Run bundle install to update Gemfile.lock
   • Commit with title Bump version to x.y.z

3. bundle exec rake release

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the MemoWise project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.