You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To improve performance for foreign key checks, we can cache successful FK checks in PgSession. This will help us avoid tserver RPCs if the same key needs to be checked repeatedly in a transaction.
This is especially handy for bulk loading of data where rows in child (FK) tables with the same foreign key are typically loaded together.
The text was updated successfully, but these errors were encountered:
Summary:
To improve performance for foreign key checks, we can cache successful FK checks in PgSession. This will help us avoid tserver RPCs if the same key needs to be checked repeatedly in a transaction.
This is especially handy for bulk loading of data where rows in child (FK) tables with the same foreign key are typically loaded together.
Performance numbers on TPCC data loading (for 2 warehouses):
Without FK cache: 17.5 mins
With FK cache: 8.5 mins (2x improvement)
Test Plan:
Jenkins
Added Java tests
Reviewers: neil, dmitry, mihnea, alex
Reviewed By: mihnea, alex
Subscribers: kannan, yql
Differential Revision: https://phabricator.dev.yugabyte.com/D7847
To improve performance for foreign key checks, we can cache successful FK checks in PgSession. This will help us avoid tserver RPCs if the same key needs to be checked repeatedly in a transaction.
This is especially handy for bulk loading of data where rows in child (FK) tables with the same foreign key are typically loaded together.
The text was updated successfully, but these errors were encountered: