Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # user >> Running Accumulo straight from Memory


Copy link to this message
-
Re: Running Accumulo straight from Memory
Yes, the effect of locality groups would be about the same in an in memory
system. The only exception would be if you're not using locality groups and
are fetching a particular column, the automatic seeking behavior of the
column filtering iterator would be more efficient with in memory rfiles.

Adam
On Sep 12, 2012 5:20 PM, "David Medinets" <[EMAIL PROTECTED]> wrote:

> Why would locality groups be useful in an in-memory system?
>
> On Wed, Sep 12, 2012 at 4:53 PM, Adam Fuchs <[EMAIL PROTECTED]> wrote:
> > Even if you are just using memory, minor and major compactions are
> important
> > to get compression, handle deletes, get sequential access (cache line
> > efficiency), use iterators, and introduce locality groups.
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB