Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
MIME-Version: 1.0
In-Reply-To: <CAPuHRiBru76XLhVPdHA_+rvVF_S3yZmmuHWjFA-ov4b3ugoVnQ@mail.gmail.com>
References: <CAPuHRiBru76XLhVPdHA_+rvVF_S3yZmmuHWjFA-ov4b3ugoVnQ@mail.gmail.com>
From: Keith Turner <keith@deenlo.com>
Date: Mon, 1 May 2017 10:52:23 -0400
Message-ID: <CAGUtCHr4v27EGO09uMrmoSg_yxaZkO8CzUhCLzPuwYFjw=bxvQ@mail.gmail.com>
Subject: Re: Accumulo Table Sacanning Taking Time!!!
To: Accumulo Dev List <dev@accumulo.apache.org>
Content-Type: text/plain; charset=UTF-8
archived-at: Mon, 01 May 2017 14:52:36 -0000

Do you know if the tablet server and/or client is CPU bound?  When you
run the query, do you see either go to 100% CPU?

For the *~1 million* records, what is the data size?  I Ask because I
am curious what the data rate is?  For example is it 2MB/sec
500KB/sec?

On Thu, Apr 27, 2017 at 7:09 AM, Suresh Prajapati
<sureshpraja1234@gmail.com> wrote:
> Hello Team
>
> I am developing a client in accumulo to store geo-spatial information and
> using geomesa for indexing on top of it. However i found that scanning *~1
> million* records taking *2-3 sec*. I looked at indexes and query plan of
> geomesa but not able to find cause of the problem. I am running accumulo as
> single tablet-server(including master). I want to know -
> what are the factors can affect accumulo scanning operation? how can I
> optimise this time?
>
> Thank You
> Suresh Prajapati