[
https://issues.apache.org/jira/browse/HBASE-14540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941276#comment-14941276
]
Elliott Clark edited comment on HBASE-14540 at 10/2/15 3:46 PM:
----------------------------------------------------------------
This will negatively impact the average response time since on average
everything will wait 2ms (1ms for wait and 1 ms for sync). So it might work for
a throughput oriented workload, it won't be all that good for a online
workloads.
was (Author: eclark):
This will negative impact the average response time since on average everything
will wait 2ms. So it might work for a throughput oriented workload, it won't be
all that good for a online workloads.
> Write Ahead Log Batching Optimization
> -------------------------------------
>
> Key: HBASE-14540
> URL: https://issues.apache.org/jira/browse/HBASE-14540
> Project: HBase
> Issue Type: Improvement
> Reporter: John Leach
> Attachments: HBaseWALBlockingWaitStrategy.java
>
>
> The new write ahead log mechanism seems to batch too few mutations when
> running inside the disruptor. As we scaled our load up (many threads with
> small writes), we saw the number of hdfs sync operations grow in concert with
> the number of writes. Generally, one would expect the size of the batches to
> grow but the number of actual sync operations to settle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
