Memory Map Files

[Nathan Schmidt]

Joel -

It's been pretty well established on this list and elsewhere that a  
core goal of memcached was to have a pool of memory more or less  
guaranteed to not cause disk IO on read or write, thus basically  
never blocking. If you want more-than-physical-RAM capacity you'd  
probably be better off using MySQL, that API is pretty well-understood.

-Nathan
	
On Jul 4, 2007, at 7:43 PM, Joel Poloney wrote:

> ... do I really need to explain this one? I thought memory mapped  
> files were pretty self explanatory. See wikipedia: http:// 
> en.wikipedia.org/wiki/Memory-mapped_file .
>
> Yes, I know there are drawbacks, but if implemented correctly, the  
> benefits far outweigh them.
>
> -- Joel
>
> On 7/5/07, Steve Grimm < sgrimm at facebook.com> wrote:
> What do you hope to gain by doing that?
>
> -Steve
>
>
>
> On 7/4/07 5:26 AM, "Joel Poloney" <jpoloney at gmail.com> wrote:
>
> Hello list,
>
> I was curious if it was possible to extend memcached to memory map  
> files as well. I know there are other memory management systems out  
> there that do this, but I would like to use only 1 memory  
> management system if possible. Memcached already deals with  
> memory... so technically this should be possible... but is it easy  
> to do, I'm not sure.
>
> Thanks!
>
> -- Joel
>
>
>