[
https://issues.apache.org/jira/browse/HBASE-16890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633279#comment-15633279
]
ramkrishna.s.vasudevan commented on HBASE-16890:
------------------------------------------------
This is my config
{code}
<property>
<name>hbase.regionserver.global.memstore.size</name>
<value>0.42</value>
</property>
<property>
<name>hfile.block.cache.size</name>
<value>0.38</value>
</property>
<property>
<name>hbase.regionserver.info.port</name>
<value>16031</value>
</property>
<property>
<name>hbase.regionserver.port</name>
<value>16041</value>
</property>
<property>
<name>hbase.master.port</name>
<value>16050</value>
</property>
<property>
<name>hbase.master.wait.on.regionservers.mintostart</name>
<value>0</value>
</property>
<property>
<name>hbase.master.info.port</name>
<value>16070</value>
</property>
<property>
<name>hbase.regionserver.handler.count</name>
<value>100</value>
</property>
<property>
<name>zookeeper.znode.parent</name>
<value>/hbase1</value>
</property>
<property>
<name>hbase.ipc.server.reservoir.enabled</name>
<value>false</value>
</property>
<property>
<name>hbase.hregion.memstore.chunkpool.maxsize</name>
<value>1</value>
</property>
<property>
<name>hbase.hregion.memstore.chunkpool.initialsize</name>
<value>0.5</value>
</property>
<property>
<name>hbase.client.rpc.codec</name>
<value>org.apache.hadoop.hbase.codec.KeyValueCodec</value>
</property>
<property>
<name>hbase.regionserver.metahandler.count</name>
<value>10</value>
</property>
<property>
<name>hbase.hregion.memstore.mslab.enabled</name>
<value>true</value>
</property>
<property>
<name>hbase.hstore.flusher.count</name>
<value>10</value>
</property>
<property>
<name>hbase.hstore.blockingStoreFiles</name>
<value>25</value>
</property>
<property>
<name>hbase.ipc.server.reservoir.initial.max</name>
<value>600</value>
</property>
<property>
<name>hbase.wal.provider</name>
<value>asyncfs</value>
</property>
{code}
I have xmx as 30G and runs with G1GC config. Do you need any other info?
> 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-rc-v2.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)
