Add fsspec optimization for improved Parquet file access performance #1030
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.
This PR implements the fsspec optimization described in the NVIDIA blog post for optimizing access to Parquet data with fsspec. The optimization enables precaching for remote file systems (e.g. S3, GCS) to improve performance when reading Parquet files.
Problem
When reading Parquet files from remote storage systems like S3 or GCS, LSDB users experience slower performance due to multiple HTTP requests for metadata and data access. The fsspec library provides built-in optimization capabilities that can significantly reduce these requests through intelligent precaching.
Solution
This PR adds optional fsspec optimization support that can be enabled through either a function parameter or environment variable:
Implementation Details
The optimization works by adding
{"precache_options": {"method": "parquet"}}
to theopen_file_options
parameter when reading Parquet files. This leverages fsspec's built-in precaching mechanism to:Key Features
open_file_options
orprecache_options
true/false
,1/0
,yes/no
,on/off
(case-insensitive)Testing
Added comprehensive test coverage including:
All existing tests continue to pass, ensuring no regressions were introduced.
Usage Examples
This implementation provides the foundation for performance testing and optimization of remote Parquet file access in LSDB workflows.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.