[
https://issues.apache.org/jira/browse/HBASE-19344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270459#comment-16270459
]
Guanghao Zhang commented on HBASE-19344:
----------------------------------------
Try the pe test with https://github.com/Apache9/hbase/tree/HBASE-19344.
{code}
./hbase org.apache.hadoop.hbase.PerformanceEvaluation --nomapred --presplit=50
--size=50 --columns=50 --valueSize=200 --writeToWAL=true --bloomFilter=NONE
randomWrite 24
Min: 904135ms Max: 914886ms Avg: 911291ms
./hbase org.apache.hadoop.hbase.PerformanceEvaluation --nomapred
--autoFlush=True --presplit=50 --size=50 --columns=50 --valueSize=200
--writeToWAL=true --bloomFilter=NONE randomWrite 24
Min: 986683ms Max: 989041ms Avg: 987935ms
{code}
The result almost same with the test result in
https://issues.apache.org/jira/browse/HBASE-17049?focusedCommentId=16268571&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16268571
> improve asyncWAL by using Independent thread for netty #IO in
> FanOutOneBlockAsyncDFSOutput
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-19344
> URL: https://issues.apache.org/jira/browse/HBASE-19344
> Project: HBase
> Issue Type: Sub-task
> Components: wal
> Affects Versions: 2.0.0-beta-1
> Reporter: Chance Li
> Assignee: Chance Li
> Fix For: 2.0.0
>
> Attachments: HBASE-19344-branch2.patch,
> HBASE-19344-branch2.patch.2.POC, wal-1-test-result.png,
> wal-8-test-result.png, ycsb_result_apache20_async_wal.pdf
>
>
> The logic now is that the netty #IO thread and asyncWal's thread are the same
> one.
> Improvement proposal:
> 1, Split into two.
> 2, All multiWal share the netty #IO thread pool.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
