[
https://issues.apache.org/jira/browse/HBASE-16890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601519#comment-15601519
]
ramkrishna.s.vasudevan commented on HBASE-16890:
------------------------------------------------
With 25000 iterations
{code}
default wal
Summary: threads=50, iterations=25000, syncInterval=0 took 28.384s
44038.895ops/s
async wal
Summary: threads=50, iterations=25000, syncInterval=0 took 30.327s
41217.398ops/s
{code}
I could see similiar output on repeated runs. Which means that when the amount
of data to be checksummed is more in async wal case we do spend lot of CPU
there. Is it possible to do this in a chunked way as did for bigger edits?
[~saint....@gmail.com]
Can you check this out and see if this stands valid in your case also.
> 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: 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)
