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

Chance Li commented on HBASE-16890:
-----------------------------------

Thanks, sir. [~Apache9]

The test result is not good enough but I think it's acceptable. pls check the 
number <<ycsb_FSHlog.vs.Async>>.  I will try more, such as fast_failover test 
that  is more important. 

bq. It is designed to be single threaded and we can use multi WAL to increase 
performance.
If we need to use multiWAL to improve performance, We hope the bottleneck is in 
the others ( such as DataStreamer#waitForAckedSeqno), not in the HBase.

bq. And for AsyncFSWAL#consume is non blocking. All I/Os are handled by netty 
asynchronously.
it's about MVCC's performance, so maybe AsyncFSWAL#sync needs to be completely 
asynchronous, not only just I/O. that means AsyncFSWAL#sync maybe can be 
improved.  I'm trying it. 
!ycsb_FSHlog.vs.Async.png!

> Analyze the performance of AsyncWAL and fix the same
> ----------------------------------------------------
>
>                 Key: HBASE-16890
>                 URL: https://issues.apache.org/jira/browse/HBASE-16890
>             Project: HBase
>          Issue Type: Sub-task
>          Components: wal
>    Affects Versions: 2.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Blocker
>             Fix For: 2.0.0-beta-1
>
>         Attachments: AsyncWAL_disruptor.patch, AsyncWAL_disruptor_1 
> (2).patch, AsyncWAL_disruptor_3.patch, AsyncWAL_disruptor_3.patch, 
> AsyncWAL_disruptor_4.patch, AsyncWAL_disruptor_6.patch, 
> HBASE-16890-rc-v2.patch, HBASE-16890-rc-v3.patch, 
> HBASE-16890-remove-contention-v1.patch, HBASE-16890-remove-contention.patch, 
> Screen Shot 2016-10-25 at 7.34.47 PM.png, Screen Shot 2016-10-25 at 7.39.07 
> PM.png, Screen Shot 2016-10-25 at 7.39.48 PM.png, Screen Shot 2016-11-04 at 
> 5.21.27 PM.png, Screen Shot 2016-11-04 at 5.30.18 PM.png, async.svg, 
> classic.svg, contention.png, contention_defaultWAL.png, 
> ycsb_FSHlog.vs.Async.png
>
>
> Tests reveal that AsyncWAL under load in single node cluster performs slower 
> than the Default WAL. This task is to analyze and see if we could fix it.
> See some discussions in the tail of JIRA HBASE-15536.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to