You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Venkatesh <vr...@aol.com> on 2010/10/08 03:33:39 UTC

Incredibly slow response to Scan

 

 J-D et.al
I've put the mapreduce issue that I had in the back burner for now.
I'm getting incredible slow response to Scan..

On a 10 node cluster for a table with 1200 regions ..it takes 20 minutes
to scan a column with given value..Got 100 or so records for the response..

Is this normal?

thanks
venkatesh
PS. setCaching(100) ..did n't make a dent in performance



Re: Incredibly slow response to Scan

Posted by Jean-Daniel Cryans <jd...@apache.org>.
If setCaching didn't make a difference, either the API isn't used
properly or the bottleneck is elsewhere.

J-D

On Thu, Oct 7, 2010 at 9:33 PM, Venkatesh <vr...@aol.com> wrote:
>
>
>
>  J-D et.al
> I've put the mapreduce issue that I had in the back burner for now.
> I'm getting incredible slow response to Scan..
>
> On a 10 node cluster for a table with 1200 regions ..it takes 20 minutes
> to scan a column with given value..Got 100 or so records for the response..
>
> Is this normal?
>
> thanks
> venkatesh
> PS. setCaching(100) ..did n't make a dent in performance
>
>
>