News for hackers. Stuff that matters.
Re:This is what 864GB of RAM looks like now by adestefan on Friday January 27, 2012 @10:45AM (#3518643)
"...russian-doll architecture of nested caching that I’ll write up in detail soon."

The details will be interesting, but that description sounds like a headache waiting to happen.

Re:This is what 864GB of RAM looks like now by raghus on Friday January 27, 2012 @01:29PM (#3519426)
The cache invalidation bit is going to be the interesting part of that write-up
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!
Re:This is what 864GB of RAM looks like now by tomjen3 on Friday January 27, 2012 @11:25AM (#3518815)
Only if you don't have good enough software engineers.

The CPU is organized that way and it works very well and that caching scheme is implemented directly on the metal. Any decent software engineer should be able to design a working implementation with an architecture that is clean.

Re:This is what 864GB of RAM looks like now by jbellis on Friday January 27, 2012 @12:35PM (#3519153)
"There are only two hard problems in Computer Science: cache invalidation and naming things."
Re:This is what 864GB of RAM looks like now by nicktelford on Friday January 27, 2012 @12:42PM (#3519193)
And off-by-one errors.
Re:This is what 864GB of RAM looks like now by wlll on Friday January 27, 2012 @12:52PM (#3519241)
"There are only three hard problems in Computer Science: cache invalidation, naming things, off-by-one errors and pedantry."
Re:This is what 864GB of RAM looks like now by Hellblazer on Saturday January 28, 2012 @07:52PM (#3523993)
All computing is an exercise is caching.
Re:This is what 864GB of RAM looks like now by nicktelford on Friday January 27, 2012 @03:29PM (#3519995)
And the Spanish Inquisition.
Re:This is what 864GB of RAM looks like now by keithnoizu on Friday January 27, 2012 @03:47PM (#3520081)
would you believe 4 things? - maxwell