You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2008/02/20 00:48:43 UTC
[jira] Commented: (HADOOP-2852) Update gridmix to avoid
artificially long tail
[ https://issues.apache.org/jira/browse/HADOOP-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570506#action_12570506 ]
Hadoop QA commented on HADOOP-2852:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12375967/2852.patch
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included +1. The patch appears to include 18 new or modified tests.
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 does not introduce any 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/1818/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1818/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1818/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1818/console
This message is automatically generated.
> Update gridmix to avoid artificially long tail
> ----------------------------------------------
>
> Key: HADOOP-2852
> URL: https://issues.apache.org/jira/browse/HADOOP-2852
> Project: Hadoop Core
> Issue Type: Test
> Components: test
> Affects Versions: 0.16.0
> Reporter: Chris Douglas
> Assignee: Chris Douglas
> Fix For: 0.16.1
>
> Attachments: 2852.patch
>
>
> The MaxEntropy test in the gridmix benchmark is submitted late into the queue, iterating past the point where the cluster is saturated. This dilutes the throughput measurement- the purpose of this benchmark- by making the tail overly dependent on the performance of a single job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.