[
https://issues.apache.org/jira/browse/CRUNCH-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389304#comment-16389304
]
Clément MATHIEU commented on CRUNCH-665:
----------------------------------------
Attached patch:
* Default values are preserved
* It is now possible to override max poll interval by setting
{{crunch.max.poll.interval}}
* Minimum poll interval is automatically computed from maximum. 1/20 seems
reasonable and was the ratio used for default values.
For the record setting {{crunch.max.poll.interval}} to 25 reduces Crunch build
time by ~2:30 min.
> Make MRExecutor pollInterval configurable
> -----------------------------------------
>
> Key: CRUNCH-665
> URL: https://issues.apache.org/jira/browse/CRUNCH-665
> Project: Crunch
> Issue Type: Improvement
> Components: Core
> Reporter: Clément MATHIEU
> Assignee: Josh Wills
> Priority: Major
> Attachments:
> 0001-CRUNCH-665-Add-crunch.max.poll.interval-property.patch,
> user-guide.mdtext.patch
>
>
> {{MRExecutor#pollInterval}} is currently hard coded to 50..1_000 for local
> mode and 500..10_000 otherwise. While being a sensible trade-off, one might
> want to poll more aggressively. For example, 1 seconds is usually too high
> for small integration tests.
> A few experiments on internal test suites showed that lowering poll interval
> could halve execution time.
> What do you think about adding a new configuration parameter that would
> override default config? I can craft a patch if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
