Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Estimate partitions number basing on a desired partition size #2289

Closed

Conversation

pomadchin
Copy link
Member

@pomadchin pomadchin commented Jul 19, 2017

This PR also introduces a new default S3GeoTiffRDD behaviour.
The question is: should we change the default reader behaviour? Or it's still should be an optional feature.

@pomadchin pomadchin requested a review from echeipesh July 19, 2017 14:18
@pomadchin pomadchin force-pushed the feature/s3geotiffrdd-opt branch 2 times, most recently from 26b5618 to c7a012c Compare July 19, 2017 14:35
…sired partition size in bytes.

Signed-off-by: Grisha Pomadchin <gr.pomadchin@gmail.com>
@echeipesh
Copy link
Contributor

To answer the question: The default behavior on principle should "just work" as much as possible.

That is not the case currently, we pretty much require partition and window size tuning before we can expect good performance. So in such a case the defaults can be changed to provide the correct behavior.

@pomadchin
Copy link
Member Author

Fixed in #2296

@pomadchin pomadchin closed this Aug 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants