[jira] [Comment Edited] (HBASE-19344) improve asyncWAL by using Independent thread for netty #IO in FanOutOneBlockAsyncDFSOutput

["Chance Li (JIRA)" <ji...@apache.org>]

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

Chance Li edited comment on HBASE-19344 at 11/30/17 3:32 AM:
-------------------------------------------------------------

These tests are based on SSD.
And the result is what we expect.
!HBASE-19344-branch.ycsb.png!


was (Author: chancelq):
These tests are based on SSD.
And the result is what we expect.
!HBASE-19344-branch.ycsb.png!

> 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-branch-ycsb-1.png, HBASE-19344-branch.ycsb.png, HBASE-19344-branch.ycsb.png, 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)