-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Search performance improvement suggestion #866
Labels
Comments
This was referenced Feb 26, 2018
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I would like to suggest to change SearchResult entity primary key from
to
By this way, when inserting many SearchResult instances for every term (specially when searching by identifiers in an attribute that contain a list of identifiers) insert statements can be packed into few statements according the batch size.
Unfortunately, insert statements cannot be packed if entity primary key cannot be determined before executing the statement because hibernate will not use batch.
Therefore, once this change is applied, rewrite statements can be enabled using this sample configuration (spring-boot style):
In order to inspect how statements are grouped, just change the JDBC url as follows:
Sample slf4j config:
Sample output in log (just two statements grouped here):
The text was updated successfully, but these errors were encountered: