[ https://issues.apache.org/jira/browse/PIG-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791810#action_12791810 ]
Hadoop QA commented on PIG-1102: -------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12428253/PIG_1102.patch against trunk revision 891499. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no tests are needed for this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. -1 release audit. The applied patch generated 406 release audit warnings (more than the trunk's current 403 warnings). -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h8.grid.sp2.yahoo.net/134/testReport/ Release audit warnings: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h8.grid.sp2.yahoo.net/134/artifact/trunk/patchprocess/releaseAuditDiffWarnings.txt Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h8.grid.sp2.yahoo.net/134/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h8.grid.sp2.yahoo.net/134/console This message is automatically generated. > Collect number of spills per job > -------------------------------- > > Key: PIG-1102 > URL: https://issues.apache.org/jira/browse/PIG-1102 > Project: Pig > Issue Type: Improvement > Reporter: Olga Natkovich > Assignee: Sriranjan Manjunath > Fix For: 0.7.0 > > Attachments: PIG_1102.patch > > > Memory shortage is one of the main performance issues in Pig. Knowing when we > spill do the disk is useful for understanding query performance and also to > see how certain changes in Pig effect that. > Other interesting stats to collect would be average CPU usage and max mem > usage but I am not sure if this information is easily retrievable. > Using Hadoop counters for this would make sense. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.