Refactoring: Switch from duckdb to Postgres for storing overture data#4
Merged
Refactoring: Switch from duckdb to Postgres for storing overture data#4
Conversation
instead of downloading through duckdb, download through aws cli and a few more tweaks to minimize memory usage
This file contains hidden or 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
1 participant
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.
Because string‐similarity searches over the Overture dataset require loading all records into memory, they suffer from high latency and excessive RAM usage. To solve this, we’ve migrated to PostgreSQL with PostGIS, which supports indexed, on‐disk queries. This PR also adds a Helm chart for Kubernetes deployment — including an init container that performs the initial data load.