[jira] [Commented] (ACCUMULO-4112) Poor performance due to MinC start/stop updates are always hsync'd

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on ACCUMULO-4112:
------------------------------------------

GitHub user keith-turner opened a pull request:

    https://github.com/apache/accumulo/pull/79

    ACCUMULO-4112 use metadata table durability config when writing minc …

    …events to walog

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/keith-turner/accumulo ACCUMULO-4112

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/accumulo/pull/79.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #79
    
----
commit 714bb77b56f8b7177421908bed44c08bc0866b93
Author: Keith Turner <kt...@apache.org>
Date:   2016-03-08T15:19:27Z

    ACCUMULO-4112 use metadata table durability config when writing minc events to walog

----


> Poor performance due to MinC start/stop updates are always hsync'd
> ------------------------------------------------------------------
>
>                 Key: ACCUMULO-4112
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4112
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>         Environment: Fluo testing on a 20-node cluster
>            Reporter: Eric Newton
>            Assignee: Keith Turner
>            Priority: Critical
>             Fix For: 1.7.2, 1.8.0
>
>         Attachments: HSyncOverheadExperiment.png, MinCFlushPerfTest.java, Sync-Flush-Log-Performance.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> [~kturner] writes:
> {quote}
> I was running a Fluo test with 1.8.0-SNAP on my workstation.  My Fluo table had a ton of tablets.   I was seeing terrible performance.   I started looking at the tserver and noticed it was always calling hsync.  I tracked down the problem to the fact that when minc start and stop events are written to the log they are always written w/ sync level.   My poor little tserver was constantly minor compacting (probably had around 600 tablets that were all being written to).  
> I changed the test config to create like 15 tablets and the performance was much better.  All cores were 100% utilized, which was not the case when hsync was always called.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)