Jan Pfeifer pfjan at
Thu Jan 11 02:56:13 UTC 2007

One thing to take care with this option is to make sure the disk can handle the throughput of the writes. 

I'm sure memcache can easily beat the disk and whatever buffer you set aside for writing to disk could eventually be overflooded.

Error handling also comes to mind ... does the cache client writer want to wait for the disk write to return (possibly and error), or should the disk write work asynchronously ? 

This is definitely a cool option in some cases, but would add lots of complexity to memcache -- complexity that I might understand others would prefer to avoid ...

just my 2¢

----- Original Message ----
From: Roberto Spadim <roberto at>
To: memcached at
Sent: Thursday, January 11, 2007 2:32:54 AM

sorry i didn't see that email wasn't sent to list

but it ONLY use disk :(
i want ONLY memory, disk just for rebuild cache when starting memcache =)

Jehiah Czebotar escreveu:
> On 1/11/07, Roberto Spadim <roberto at> wrote:
>> could we implement an non volatile inteface to memcache server too?
>> like every 5 seconds write to disk and when server end too
>> in the next startup server can reload data from disk and i avoid
>> recaching from my applications
> no need to write an interface to memcached; such a thing already
> exists and is called Tugela Cache. It's basically a memcached server
> that saves data in a berkeley db file instead of memory which sounds
> like exactly what you are looking for

Need a quick answer? Get one in minutes from people who know.
Ask your question on

More information about the memcached mailing list