CaiSijie wrote:
Thank you for your replay.
My version of HBase is 0.18.0. Yes, I read data in series.
But what I see is that reading 1st data cost least time and reading 128th
data cost most time. It means that time increase from reading 1st to 128th
data item. Then when reading 129th data item
we do serial search forward from the closest index position.
>
> What version of hbase are you using?
>
> You are doing your reads in series?
>
> This is really interesting stuff. Can you dig in some more and try and
> figure whats going on?
>
> Thanks Cai.
>
> St.Ac
The only thing that comes to mind is that by default in hadoop, the
mapfile index interval is 128; every 128th entry in mapfile gets an
entry in the mapfile index. Only, in hbase, we change the default
interval to be 32. Check to make sure you are picking up
hbase.io.index.interval of 32.
Otherwis
Hi all,
Our environment is 4　machines ( 1 is also slave).
They are all region servers.
First I write 1000 item data to the hbase. Then I reading data according to
writing sequence. And then I check the data reading performance.
I draw a graph (x-ray is data item number, y-ray is data reading's
