[
https://issues.apache.org/jira/browse/PIG-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602627#action_12602627
]
Pi Song commented on PIG-200:
-----------------------------
To move this forward, I propose that we should have:-
1) Small dataset test. Just a set of simple benchmarks for running on
development box. For a common machine, it shouldn't take longer than 30 minutes
in total.
2) Large dataset test. For real benchmarking.
I think the test cases in http://wiki.apache.org/pig/PigPerformance should
already provide good coverage. We will have to do another review once query
optimizer is in place.
Alan, could you please attach the perl script so that I can see what it does?
> Pig Performance Benchmarks
> --------------------------
>
> Key: PIG-200
> URL: https://issues.apache.org/jira/browse/PIG-200
> Project: Pig
> Issue Type: Task
> Reporter: Amir Youssefi
> Assignee: Amir Youssefi
>
> 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.
