final Scan scan = new Scan(startInclusive, endExclusive)
.addFamily(stage.getBytes())
.setCaching(DEFAULT_BATCH_SIZE)
.setCacheBlocks(false);
Here is the scan test code. This will return ~1MM rows from both tables,
while limiting scan to a single column family..
Thanks.
On Mon, Aug 21, 2017 at 2:16 PM, Partha <parthaema...@gmail.com> wrote:
> addFamily only. There is only 1 column/qualifier per column family
>
>
> On Aug 21, 2017 2:05 PM, "Anoop John" <anoop.hb...@gmail.com> wrote:
>
> In ur test are u using Scan#addColumn(byte [] family, byte []
> qualifier) or it is addFamily(byte [] family) only?
>
> On Mon, Aug 21, 2017 at 10:02 PM, Partha <parthaema...@gmail.com> wrote:
> > Block cache is disabled on both scan tests. Setcaching is set to 500 in
> both
> > scans. Hbase version is 1.1.2.2.6.0.3-8
> >
> > Will post client scan test code.
> >
> > Thanks
> >
> >
> > On Aug 21, 2017 8:57 AM, "Anoop John" <anoop.hb...@gmail.com> wrote:
> >
> > I was abt to ask to whether have run the tests after a major
> > compaction. But there also u are facing same issue it seems !
> >
> > Which version of HBase?
> >
> > Block cache been used? What are the size and configs related to cache?
> >
> > Can u pls paste the exact client side code been used in tests?
> >
> > -Anoop-
> >
> > On Sun, Aug 20, 2017 at 4:36 AM, Partha <parthaema...@gmail.com> wrote:
> >> Anoop,
> >>
> >> Yes, each column family (in both tables) uses the same encoding
> >> (fast-diff)
> >> and same compression (gzip).
> >>
> >> I suggest you to just try the simple test as my case and see if you
> notice
> >> a
> >> similar drop in performance (almost linear to the # of column families)
> >
> >
>
>
>
