[
https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442439#comment-16442439
]
ramkrishna.s.vasudevan edited comment on HBASE-20188 at 4/18/18 12:53 PM:
--------------------------------------------------------------------------
I am not before system now.
For 2.0 comparison between STREAM and PREAD it is 30 secs vs 27 secs for a
simple scan of 10G.
97 vs 27 is for 2.0 vs 1.2. As I said I will dig in deeper as to what exactly
is happening in 1.2 and 2.0 and report back here. Just give a day or two.
HDFS is 2.7.3 and I have some HDD and not SSDs in my small cluster.
Sorry, typo difficult when not in actual system.
For 2.0 comparison between STREAM and PREAD it is 30 secs vs 97 secs for a
simple scan of 10G.
was (Author: ram_krish):
I am not before system now.
For 2.0 comparison between STREAM and PREAD it is 30 secs vs 27 secs for a
simple scan of 10G.
97 vs 27 is for 2.0 vs 1.2. As I said I will dig in deeper as to what exactly
is happening in 1.2 and 2.0 and report back here. Just give a day or two.
HDFS is 2.7.3 and I have some HDD and not SSDs in my small cluster.
> [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, 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, 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, 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)
