hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16890) Analyze the performance of AsyncWAL and fix the same
Date Fri, 11 Nov 2016 10:26:58 GMT

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

ramkrishna.s.vasudevan commented on HBASE-16890:
------------------------------------------------

With checksum disabled and with 10G of data with 50 threads, we can assume  that the number
of sync futures that gets created are almost same, then I could see that there are around
2000 additional syncs that are waiting for around 100 to 300 ms to get done.
In FSHLOG case syncs waiting betwenn 100 to 300 ms is 2300 where as in AsyncFSHLog it is 4100.
As stated in my previous comment I see that the flushes and log rolls are over all same.

> 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
>             Fix For: 2.0.0
>
>         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
>
>
> 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.3.4#6332)

Mime
View raw message