[
https://issues.apache.org/jira/browse/HBASE-16890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632624#comment-15632624
]
Duo Zhang commented on HBASE-16890:
-----------------------------------
I've changed the WALPE code to
{code}
long txid = wal.append(hri, logkey, walEdit, true);
if (!this.noSync) {
if (++lastSync >= this.syncInterval) {
wal.sync(txid);
lastSync = 0;
}
}
{code}
Nothing changed... FSHLog is still the slowest...
This is really weird. [~ram_krish] Can you please run your test again on a
normal cluster with at least three DNs to see if AsyncFSWAL is still slower?
Thanks.
> 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, 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, 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)
