You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2019/02/13 02:08:00 UTC

[jira] [Updated] (HBASE-20188) [TESTING] Performance

     [ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guanghao Zhang updated HBASE-20188:
-----------------------------------
    Fix Version/s:     (was: 2.2.0)
                   2.3.0

> [TESTING] Performance
> ---------------------
>
>                 Key: HBASE-20188
>                 URL: https://issues.apache.org/jira/browse/HBASE-20188
>             Project: HBase
>          Issue Type: Umbrella
>          Components: Performance
>            Reporter: stack
>            Priority: Blocker
>             Fix For: 3.0.0, 2.3.0
>
>         Attachments: CAM-CONFIG-V01.patch, HBASE-20188-xac.sh, HBASE-20188.sh, HBase 2.0 performance evaluation - 8GB(1).pdf, HBase 2.0 performance evaluation - 8GB.pdf, HBase 2.0 performance evaluation - Basic vs None_ system settings.pdf, HBase 2.0 performance evaluation - throughput SSD_HDD.pdf, 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_CPU.png, YCSB_GC_TIME.png, YCSB_IN_MEMORY_COMPACTION=NONE.ops.png, YCSB_MEMSTORE.png, YCSB_OPs.png, YCSB_in-memory-compaction=NONE.ops.png, YCSB_load.png, flamegraph-1072.1.svg, flamegraph-1072.2.svg, hbase-env.sh, hbase-site.xml, hbase-site.xml, hits.png, hits_with_fp_scheduler.png, lock.127.workloadc.20180402T200918Z.svg, lock.2.memsize2.c.20180403T160257Z.svg, perregion.png, run_ycsb.sh, total.png, tree.txt, workloadx, workloadx
>
>
> 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
(v7.6.3#76005)