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

stack edited comment on HBASE-16890 at 12/11/17 8:14 PM:
---------------------------------------------------------

128 threads. Did two runs of first and last just to be sure of what I was 
seeing.

||workload||oldFSHLog||oldFSHLog||async||async+own_eventloop||async+own_eventloop||
|load|15063 ops/s|14536 ops/s|18014 ops/s|17542 ops/s|15943 ops/s|
|a|34080 ops/s|34610 ops/s|53664 ops/s|51549 ops/s|49365 ops/s|
|w|26032 ops/s|25999 ops/s|53122 ops/s|53207 ops/s|52435 ops/s|

So, +1 on making asyncwal default WAL client. It shows better in these yscb 
tests and we can improve it further. Having its own eventloop usually helps 
some but sometimes doesn't. Leave this off by default.

Let me check the issue w/ 2.8.


was (Author: stack):
128 threads. Did two runs of first and last just to be sure of what I was 
seeing.

||workload||oldFSHLog||oldFSHLog||async||async+own_eventloop||async+own_eventloop||
|load|15063 ops/s|14536 ops/s|18014 ops/s|17542 ops/s|15943 ops/s|
|a|34080 ops/s|34610 ops/s|53664 ops/s|51549 ops/s|49365 ops/s|
|w|26032 ops/s|25999 ops/s|53122 ops/s|53207 ops/s|52435 ops/s|

So, +1 on making async+own_eventloop default WAL client. It shows better in 
these yscb tests and we can improve it further.

Let me check the issue w/ 2.8.

> 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