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.

Sign up for GitHub

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

Jump to bottom

Improve Postgres subsetting performance #51

Open
evoxmusic opened this issue Apr 24, 2022 · 1 comment
Open

Improve Postgres subsetting performance #51

evoxmusic opened this issue Apr 24, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@evoxmusic
Copy link
Contributor

I've tried to subset a Postgres DB of 2GB of data and RepliByte took 38 minutes to complete. I suspect the function subset.postgres.filter_insert_into_rows(..) to be the bottleneck since it is called multiple times and scan the entire file (even if there is a small index).

Something that can be done to drastically reduce the time would be to split the dump into multiple table files. Then scan will be limited to the table.
@evoxmusic evoxmusic added the enhancement New feature or request label Apr 24, 2022
@evoxmusic
Copy link
Contributor Author

Note: performances depend on how deep is the graph. My testing database contains 41 tables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@evoxmusic