enabled gdal multirange, needs ulimit -n 8192 #345
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GDAL_HTTP_MULTIRANGE has been enabled but it requires larger than default per process max file descriptor limit.
On ubuntu add entry to /etc/security/limits.conf
Do something similar for docker images.
With multirange enabled GDAL curl driver will open several tcp sockets and request ranges data over multiple connections. This can speed up downloads up to 25% to 30% for some data sets (ESA worldcover).
With multirange enabled and default nofile set to 1024 both selftest and subset_perf_test fail. They should pass after nofile limit has been increased.