News for hackers. Stuff that matters.
Re:This is what 864GB of RAM looks like now by dhh on Friday January 27, 2012 @02:48PM (#3519842)
I'll give away that secret right now: Key-based expiration.
Re:This is what 864GB of RAM looks like now by codyrobbins on Friday January 27, 2012 @03:09PM (#3519924)
Are you defining dependencies between the keys somehow so that keys invalidated further down in the hierarchy propagate up to invalidations all the way up the stack?
Re:This is what 864GB of RAM looks like now by vbo on Saturday January 28, 2012 @03:20AM (#3521619)
We do this to invalidate multiple keys at once. All related keys are created based on a master key (well, the value of that key). Once that is changed, all keys are invalidated.
Re:This is what 864GB of RAM looks like now by dhh on Saturday January 28, 2012 @06:40AM (#3521864)
Key-dependency is achieved using touch-parent-on-update.
Re:This is what 864GB of RAM looks like now by codyrobbins on Saturday January 28, 2012 @03:13PM (#3523079)
Whoa—I can’t believe this #cache_key and :touch stuff was introduced years ago and I somehow completely missed it. This is the most useful and elegant thing ever!