splitwise / cacheable Goto Github PK

As far as I can tell from source code there is no memoization of fetched cache value for later cached method calls on the same object. Is it on purpose?

To be honest, this behavior seems to be pretty surprising:

class Foo
  include Cacheable
  cacheable :bar

  def bar
    "foo"
  end
end

foo = Foo.new

foo.bar # cache read and deserialization
foo.bar # cache read and deserialization
foo.bar # cache read and deserialization

Context: recently I saw a Rails app in the wild that cached some ActiveRecord model methods that in turn returned another ActiveRecord objects. And some places got terribly slow due to dozens of repeated calls to retrieve and deserialize which is especially slow and compute-intensive for AR objects, see this blog post for details (and yes, I know that doing so is a bad idea per se). So I had to get rid of cacheable in favor of pure memoization or manual caching with following memoization.

Redis is pretty great. Why not try and support it out of the box?

Hello there,

I am trying to cache methods calling Github API, all of them are working properly, except one in some specific conditions: It's retrieving a super long list of repositories (8200). So, I was wondering, if the value to store it's way to big, it's not being cached? How can I check that? Is there a log or something?

Thanks.

For example it will fail if used inside Foo::Bar::BazController. Detailed error report and stack trace to come.

Hello, I've started to develop a gem with the same intent and similar syntax this week. While doing some research I ended up finding this gem and I wanted to know if it is still being maintained