Mailing-List: contact pig-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pig-dev@hadoop.apache.org
Message-ID: <21099061.223561278451196323.JavaMail.jira@thor>
Date: Tue, 6 Jul 2010 17:19:56 -0400 (EDT)
From: "Daniel Dai (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Subject: [jira] Updated: (PIG-200) Pig Performance Benchmarks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/PIG-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Dai updated PIG-200:
---------------------------

    Attachment:     (was: pigmix2.patch)

> Pig Performance Benchmarks
> --------------------------
>
>                 Key: PIG-200
>                 URL: https://issues.apache.org/jira/browse/PIG-200
>             Project: Pig
>          Issue Type: Task
>            Reporter: Amir Youssefi
>            Assignee: Alan Gates
>             Fix For: 0.2.0
>
>         Attachments: generate_data.pl, perf-0.6.patch, perf.hadoop.patch, perf.patch, pigmix2.patch
>
>
> To benchmark Pig performance, we need to have a TPC-H like Large Data Set plus Script Collection. This is used in comparison of different Pig releases, Pig vs. other systems (e.g. Pig + Hadoop vs. Hadoop Only).
> Here is Wiki for small tests: http://wiki.apache.org/pig/PigPerformance
> I am currently running long-running Pig scripts over data-sets in the order of tens of TBs. Next step is hundreds of TBs.
> We need to have an open large-data set (open source scripts which generate data-set) and detailed scripts for important operations such as ORDER, AGGREGATION etc.
> We can call those the Pig Workouts: Cardio (short processing), Marathon (long running scripts) and Triathlon (Mix). 
> I will update this JIRA with more details of current activities soon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.