hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: HBase Performance
Date Fri, 10 Feb 2017 14:42:18 GMT
Can you describe your use cases ?

e.g. TTL is currently set to FOREVER. If you can set to lower TTL, some
obsolete data would be compacted away after TTL expires.

Cheers

On Fri, Feb 10, 2017 at 6:17 AM, Devi Sunil Kumar Shegu <
sunil143devi@gmail.com> wrote:

> Increase both read n write performance.
>
> Sure will add more nodes.
>
>
>
> On Feb 10, 2017 19:44, "Ted Yu" <yuzhihong@gmail.com> wrote:
>
> Do you want to increase performance for reads, writes or both ?
>
> Your table is presplit. Can you add more node to leverage the multiple
> regions ?
>
> If you need better performance for reads, consider using BucketCache.
>
> Cheers
>
> > On Feb 10, 2017, at 2:22 AM, Devi Sunil Kumar Shegu <
> sunil143devi@gmail.com> wrote:
> >
> > Hi ,
> >
> > 1) I have 1 Master node and 1 Slave node
> > 2) Created a table with the below query
> > create 'my_table', 'u', { NUMREGIONS => 16, SPLITALGO =>
> 'HexStringSplit'}
> > 3) All the regions are in the single slave Node
> > 4) Here is the table description
> >
> > {NAME => 'u', BLOOMFILTER => 'ROW', VERSIONS => '1', IN_MEMORY =>
> 'false',
> > KEEP_DELETED_CELLS => 'FALSE', DATA_BLOCK_ENCODING => 'NONE', TTL =>
> > 'FOREVER', COMPRESSION => 'NONE', MIN_VERSIONS => '0', BLOCKCACHE =>
> > 'true', BLOCKSIZE => '65536', REPLICATION_SCOPE => '0'}
> >
> > How can I improve performance? by changing the compression or any other
> > options?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message