<div>
            <div>
                <span>Michael,</span></div><div><span><br></span></div><div><span>You might want to check out riak_kv_ets_backend, riak_kv_gb_trees_backend, and riak_kv_cache_backend.</span></div><div><span><br></span></div><div><span><a href="http://wiki.basho.com/Configuration-Files.html">http://wiki.basho.com/Configuration-Files.html</a></span></div><div><span><br></span></div><div><span><a href="http://wiki.basho.com/Configuration-Files.html"></a>-Greg<br>
                </span>
                <span></span>
                
                <p style="color: #a0a0a0;">On Friday, May 27, 2011 at 10:35 PM, Michael McClain wrote:</p>
                <blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
                    <span><div><div>Hi,<br><br> Is it possible to store the whole database in memory?<br> In a similar way as Redis does.<br><br> I'm really interested in the distributed map reduce done by riak ("bring processing to the data, instead of data to processors), but I need faster writes/reads that a memory-only database could provide.<br>
 In case you don't support memory-only storage (no disk touched / all keys and data fitting the memory in all nodes) yet, do you plan on implementing it?<br><br>Thank you,<br>Michael<br>
</div><div>_______________________________________________<br>riak-users mailing list<br><a href="mailto:riak-users@lists.basho.com">riak-users@lists.basho.com</a><br><a href="http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com">http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com</a><br></div></div></span>
                
                
                
                
                </blockquote>
                
                <div>
                    <br>
                </div>
            </div>
        </div>