<HTML>
<HEAD>
<TITLE>Re: Memory Map Files</TITLE>
</HEAD>
<BODY>
<FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Yes, thanks, I think we all know what memory-mapped files are! Do you hope to gain:<BR>
<BR>
</SPAN></FONT><UL><LI><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Bigger cache sizes by mapping a file bigger than physical memory?
</SPAN></FONT><LI><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Caches that persist across restarts?
</SPAN></FONT><LI><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Caches that you can share among concurrently running memcached processes by pointing them at the same file?
</SPAN></FONT><LI><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Caches that can be directly accessed by client applications by pointing them at the file maintained by memcached?
</SPAN></FONT><LI><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Caches that can be accessed remotely using a network filesystem?
</SPAN></FONT><LI><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Administrative benefits (e.g., setting the cache size by changing the file size)?
</SPAN></FONT><LI><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Performance benefits?<BR>
</SPAN></FONT></UL><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
Hopefully that list makes it clear that “What do you hope to gain?” is not an idiotic question. You could be looking for any or all of those things. What feature(s), specifically, do you want to have that memcached as it currently exists doesn’t provide? Are you looking specifically for one of the above benefits, some combination of them, or something else entirely?<BR>
<BR>
-Steve<BR>
<BR>
<BR>
On 7/4/07 7:43 PM, "Joel Poloney" <jpoloney@gmail.com> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>... do I really need to explain this one? I thought memory mapped files were pretty self explanatory. See wikipedia: <a href="http://en.wikipedia.org/wiki/Memory-mapped_file">http://en.wikipedia.org/wiki/Memory-mapped_file</a> <a href="http://en.wikipedia.org/wiki/Memory-mapped_file"><http://en.wikipedia.org/wiki/Memory-mapped_file></a> .<BR>
<BR>
Yes, I know there are drawbacks, but if implemented correctly, the benefits far outweigh them.<BR>
<BR>
-- Joel<BR>
<BR>
On 7/5/07, <B>Steve Grimm</B> < sgrimm@facebook.com <a href="mailto:sgrimm@facebook.com"><mailto:sgrimm@facebook.com></a> > wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>What do you hope to gain by doing that?<BR>
<BR>
-Steve<BR>
<BR>
<BR>
<BR>
On 7/4/07 5:26 AM, "Joel Poloney" <jpoloney@gmail.com> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Hello list,<BR>
<BR>
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. <BR>
<BR>
Thanks!<BR>
<BR>
-- Joel<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
</SPAN></FONT>
</BODY>
</HTML>