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.

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

Table size and transformation scoring #53

Merged
merged 1 commit into from
Apr 4, 2024
Merged

Table size and transformation scoring #53

merged 1 commit into from
Apr 4, 2024

Conversation

wwoytenko
Copy link
Contributor

  • Added tables scoring according to their size and transformation count. It should help to distribute the dumper tasks equally to the workers (Table ordering during dump / restore #50). The transformer score is 0.03 for table size
  • Fixed pgx rows object leakage during the schema introspection stage

* Added tables scoring according to their size and transformation count. It should help to distribute the dumper tasks equally to the workers (#50). The transformer score is 0.03 for table size
* Fixed pgx rows object leakage during the schema introspection stage
@wwoytenko wwoytenko added the enhancement New feature or request label Apr 4, 2024
@wwoytenko wwoytenko self-assigned this Apr 4, 2024
@wwoytenko wwoytenko merged commit 944ecda into main Apr 4, 2024
15 checks passed
@wwoytenko wwoytenko deleted the tables_scoring branch April 4, 2024 16:03
@@ -351,6 +361,7 @@ func BuildTableSearchQuery(
n.nspname as "Schema",
c.relname as "Name",
pg_catalog.pg_get_userbyid(c.relowner) as "Owner",
pg_catalog.pg_relation_size(c.oid) as "Size",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wwoytenko did you consider using pg_table_size here, since that includes TOAST?

This PR definitely improves the situation, and most of our big tables are processes first, but the biggest of them all still ends up being the bottleneck because most of the data is in TOAST

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, important remark. I will renew the size calculation in the new PR

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@janmeier should be fixed in #71

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

Successfully merging this pull request may close these issues.

2 participants