hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-20188) [TESTING] Performance
Date Tue, 03 Apr 2018 07:22:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423581#comment-16423581

ramkrishna.s.vasudevan commented on HBASE-20188:

bq.None really. Tried with data cached thinking it i/o that was responsible for the difference,
but while it brings us closer, we are still down from hbase1.2.7 (52221.77 ops/second vs 33839.57).

This is really surprising. Even after data cache you see hbase-2 to be so much slower? All
are defaults in both cases? What about bloom filters? What is the cache size here? And you
sure all data is served only from cache?

> [TESTING] Performance
> ---------------------
>                 Key: HBASE-20188
>                 URL: https://issues.apache.org/jira/browse/HBASE-20188
>             Project: HBase
>          Issue Type: Umbrella
>          Components: Performance
>            Reporter: stack
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 2.0.0
>         Attachments: CAM-CONFIG-V01.patch, ITBLL2.5B_1.2.7vs2.0.0_cpu.png, ITBLL2.5B_1.2.7vs2.0.0_gctime.png,
ITBLL2.5B_1.2.7vs2.0.0_iops.png, ITBLL2.5B_1.2.7vs2.0.0_load.png, ITBLL2.5B_1.2.7vs2.0.0_memheap.png,
ITBLL2.5B_1.2.7vs2.0.0_memstore.png, ITBLL2.5B_1.2.7vs2.0.0_ops.png, ITBLL2.5B_1.2.7vs2.0.0_ops_NOT_summing_regions.png,
YCSB_OPs.png, YCSB_in-memory-compaction=NONE.ops.png, YCSB_load.png, flamegraph-1072.1.svg,
flamegraph-1072.2.svg, tree.txt
> How does 2.0.0 compare to old versions? Is it faster, slower? There is rumor that it
is much slower, that the problem is the asyncwal writing. Does in-memory compaction slow us
down or speed us up? What happens when you enable offheaping?
> Keep notes here in this umbrella issue. Need to be able to say something about perf when
2.0.0 ships.

This message was sent by Atlassian JIRA

View raw message