Mailing-List: contact accumulo-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: accumulo-user@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <4EB0528C.6090909@digitalreasoning.com>
References: <4EA8665A.6060805@digitalreasoning.com>
	<CAPMpPc7_Kk+T7PH=u7Jvxg+ruepN78+ZcBH0VJ3Reg8JS==75A@mail.gmail.com>
	<CAGUtCHpGxa-JM_UOXNrFapiRZ3PYXUdAxMHErVpPN+T0eMVCQQ@mail.gmail.com>
	<4EB0528C.6090909@digitalreasoning.com>
Date: Wed, 2 Nov 2011 14:36:42 -0400
Message-ID: 
 <CAGUtCHrfqWS9i+ycEpjmC6aCK0a0Zbpr9W7MKD1tcb78-+Obpg@mail.gmail.com>
Subject: Re: Scanning for rows using columnfamily only
From: Keith Turner <keith@deenlo.com>
To: accumulo-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 1, 2011 at 4:11 PM, Keith Massey
<keith.massey@digitalreasoning.com> wrote:
> Thanks for the tips. We tried using one locality group per column family (I
> think there are 20-25). It has definitely sped up queries for all data in a
> single column family. The first batch comes back in about 5 seconds rather
> than 120 seconds without the locality groups. Our data load time doubled
> though from 7 hours to 14 hours. I don't have any evidence at this point
> that it is related to the locality groups. But there were very few
> differences between the 7-hour load and the 14-hour load. Any thoughts about
> whether this could be a side effect of loading data into 25 locality groups?
> Or am I looking in the wrong place?
> Thanks again.
>
> Keith
>

I ran some experiments w/ different numbers of locality groups, it had
a noticeable effect on minor compactions times.  The results are in a
comment in ticket ACCUMULO-112. I suspect the locality group change is
behind the slowdown in ingest.

https://issues.apache.org/jira/browse/ACCUMULO-112