[
https://issues.apache.org/jira/browse/HADOOP-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565164#action_12565164
]
Hadoop QA commented on HADOOP-2768:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12374633/perf1.patch
against trunk revision 616796.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler
warnings.
release audit +1. The applied patch does not generate any new release
audit warnings.
findbugs -1. The patch appears to introduce 1 new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1733/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1733/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1733/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1733/console
This message is automatically generated.
> DFSIO write performance benchmark shows a regression
> ----------------------------------------------------
>
> Key: HADOOP-2768
> URL: https://issues.apache.org/jira/browse/HADOOP-2768
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: Mukund Madhugiri
> Assignee: dhruba borthakur
> Priority: Blocker
> Fix For: 0.16.0
>
> Attachments: perf.patch, perf.patch, perf1.patch
>
>
> We are seeing a performance regression in DFSIO write benchmark, possibly due
> to Hadoop-1707.
> Here is the data:
> - Aggregate cluster throughput went from 0.30G to 0.14G with 39 concurrent
> clients, on 20 nodes
> - Aggregate cluster throughput went from 1.15G to 0.85G with 39 concurrent
> clients, on 100 nodes
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
