Phillip B Oldham wrote:
I'm looking for a solution which involves an in-memory cache of "hot"
records which are persisted to disk on modification and when they go
"cold", returning to the memory store on request. I've not found
anything yet that meets my needs, so I'm going to have to either throw
something together or give up and try and use some sort of RDBMS with
a cache layer.
What you seem to be describing there is the way most filesystems work,
as long as you're not calling fsync() or opening files with
O_DSYNC/O_DIRECT. Is the challenge that you need this to be available
over the network through something like memcached protocol?
Are you trying to solve for long lived cache items or caches which must
be larger than available DRAM?
- Matt
On Oct 8, 2:36 pm, "Josef Finsel" <[EMAIL PROTECTED]> wrote:
Just out of curiosity, what are you looking to gain by this?
On Wed, Oct 8, 2008 at 9:01 AM, Phillip B Oldham
<[EMAIL PROTECTED]>wrote:
Is it possible to monitor memcached to find out when records have been
added, changed, removed, or automatically dropped?
--
"If you see a whole thing - it seems that it's always beautiful. Planets,
lives... But up close a world's all dirt and rocks. And day to day, life's a
hard job, you get tired, you lose the pattern."
Ursula K. Le Guin
