Skip to content
New issue

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

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

Already on GitHub? # to your account

Merge consecutive Requests #23

Closed
vincentsarago opened this issue May 26, 2020 · 2 comments
Closed

Merge consecutive Requests #23

vincentsarago opened this issue May 26, 2020 · 2 comments

Comments

@vincentsarago
Copy link
Contributor

linked to #21, GDAL merge consecutive requests (horizontal tiles, when band interleave I think) up to 2Mb (configurable).

Partial downloads (requires the HTTP server to support random reading) are done with a 16 KB granularity by default. Starting with GDAL 2.3, the chunk size can be configured with the CPL_VSIL_CURL_CHUNK_SIZE configuration option, with a value in bytes. If the driver detects sequential reading it will progressively increase the chunk size up to 2 MB to improve download performance. Starting with GDAL 2.3, the GDAL_INGESTED_BYTES_AT_OPEN configuration option can be set to impose the number of bytes read in one GET call at file opening (can help performance to read Cloud optimized geotiff with a large header).

Ref: https://gdal.org/user/virtual_file_systems.html#virtual-file-systems

@geospatial-jeff
Copy link
Owner

For reference, I closed #21 after my initial tests for merging consecutive ranges but I was merging across rows and columns with a pretty large COG which explains why it was so slow.

Will retry with horizontal tiles/band interleave.

@geospatial-jeff
Copy link
Owner

Closed with #33

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants