[
https://issues.apache.org/jira/browse/BIGTOP-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761469#comment-13761469
]
jay vyas commented on BIGTOP-1057:
----------------------------------
Good point roman - yes its certainly okay for small clusters:
teragen 10 = 10 rows of 100bytes -> 1000 bytes -> 1 KB
teragen 1000 = 1000 rows of 100 bytes -> 100 KB
And the default value is 1000, so we are in good shape :)
$> ls -altrh data/teragen1000
total 114K
drwxr-xr-x. 39 root root 8.0K Sep 8 11:16 ..
drwxr-xr-x. 3 root root 4.1K Sep 8 11:16 _logs
-rwxrwxrwx. 1 root root 49K Sep 8 11:16 part-00000
-rwxrwxrwx. 1 root root 49K Sep 8 11:16 part-00001
-rwxrwxrwx. 1 root root 0 Sep 8 11:16 _SUCCESS
drwxrwxrwx. 3 root root 4.1K Sep 8 11:16 .
> Add TeraGen / TeraSort Benchmakring
> -----------------------------------
>
> Key: BIGTOP-1057
> URL: https://issues.apache.org/jira/browse/BIGTOP-1057
> Project: Bigtop
> Issue Type: Test
> Components: Tests
> Reporter: jay vyas
> Assignee: jay vyas
> Attachments: BIGTOP-1057.1.patch, BIGTOP-1057.1.patch,
> BIGTOP-1057.1.patch
>
>
> Benchmarking is indeed on the road map for bigtop , as per a recent mailing
> list thread. Lets add in Terasort / Teragen as a starting point.
> Two to note when adding this module:
> First - This can be done
> 1) either in a new test-artifacts submodule (i.e. called benchmarking), or
> else,
> 2) it can be added individually into ecosystem components.
> Second - Parameterization of the tests from the pom file will make it so that
> the initial tests really are just smokes, and they can be changed over time
> to be real performance benchmarks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
