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

stack commented on HBASE-20188:
-------------------------------

Here is what I've been running:
{code}
stack@ve0524:~$ ./bin/run_ycsb.sh
+ set -e
+ RECORD_COUNT=25000000
+ INSERT_COUNT=25000000
+ OFFSET_SOURCE=/home/stack/bin/host_offset.txt
+ YCSB=/home/stack/ycsb/bin/ycsb
+ WORKLOADS=/home/stack/ycsb/workloads
++ hostname
+ HERE=ve0524
+ [[ -f /home/stack/bin/host_offset.txt ]]
+ OFFSET=0
+ TIMED_EXEC_ARGS=(-s -p maxexecutiontime=${MAX_TIME} -jvm-args='-Xmx8192m 
-Djava.security.egd=file:/dev/./urandom ')
+ EXEC_ARGS=(-s -jvm-args='-Xmx8192m -Djava.security.egd=file:/dev/./urandom ')
+ case "$BINDING" in
+ BINDING_ARGS=(-threads 48 -cp ~/conf_hbase -p columnfamily=family)
+ WORKLOAD_LOAD_ARGS=(-p table=ycsb "${BINDING_ARGS[@]}" "${EXEC_ARGS[@]}")
+ WORKLOAD_ARGS=(-p table=ycsb "${BINDING_ARGS[@]}" "${TIMED_EXEC_ARGS[@]}")
+ WORKLOADE_ARGS=(-p table=ycsb_workloade "${BINDING_ARGS[@]}" 
"${EXEC_ARGS[@]}")
++ date
+ echo 'Thu Mar 29 18:28:13 PDT 2018 loading'
Thu Mar 29 18:28:13 PDT 2018 loading
+ perf stat /home/stack/ycsb/bin/ycsb load hbase12 -P 
/home/stack/ycsb/workloads/workloada -p table=ycsb -threads 48 -cp 
/home/stack/conf_hbase -p columnfamily=family -s '-jvm-args=-Xmx8192m 
-Djava.security.egd=file:/dev/./urandom ' -p recordcount=25000000 -p 
exportfile=logs/ycsb-load-measurements-ve0524-20180330T01:28:13Z.json -p 
exporter=com.yahoo.ycsb.measurements.exporter.JSONArrayMeasurementsExporter
++ date
+ echo 'Thu Mar 29 18:57:30 PDT 2018 50/50 workload a'
Thu Mar 29 18:57:30 PDT 2018 50/50 workload a
+ /home/stack/ycsb/bin/ycsb run hbase12 -P /home/stack/ycsb/workloads/workloada 
-p table=ycsb -threads 48 -cp /home/stack/conf_hbase -p columnfamily=family -s 
-p maxexecutiontime=1200 '-jvm-args=-Xmx8192m 
-Djava.security.egd=file:/dev/./urandom ' -p recordcount=0 -p 
operationcount=25000000 -p 
exportfile=logs/ycsb-workloada-measurements-ve0524-20180330T01:28:13Z.json -p 
exporter=com.yahoo.ycsb.measurements.exporter.JSONArrayMeasurementsExporter
...
++ date
+ echo 'Thu Mar 29 19:06:08 PDT 2018 workload c'
Thu Mar 29 19:06:08 PDT 2018 workload c
+ perf stat /home/stack/ycsb/bin/ycsb run hbase12 -P 
/home/stack/ycsb/workloads/workloadc -p table=ycsb -threads 48 -cp 
/home/stack/conf_hbase -p columnfamily=family -s -p maxexecutiontime=1200 
'-jvm-args=-Xmx8192m -Djava.security.egd=file:/dev/./urandom ' -p 
recordcount=25000000 -p operationcount=25000000 -p 
exportfile=logs/ycsb-workloadc-measurements-ve0524-20180330T01:28:13Z.json -p 
exporter=com.yahoo.ycsb.measurements.exporter.JSONArrayMeasurementsExporter
++ date
+ echo 'Thu Mar 29 19:26:09 PDT 2018 done'
{code}

> [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: 2.0.0
>
>         Attachments: 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, 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
(v7.6.3#76005)

Reply via email to