Async liquibase #526
Closed
Async liquibase #526
Conversation
This file contains 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
Signed-off-by: Bonczidai Levente <[email protected]>
|
committed a poc - if you activate the mechanism (uncomment the hibernate gives the exception, it tries to access the DB but it is not ready since liquibase is doing it on another thread - seems to me that everyhing is dependent on everything here (can we do it parallel?) - anyway the time used by liquibase is around 1,5 sec (not 7-8 like in the example) I am not sure there is an easy way to achieve async loading - do you think otherwise? |
|
It wasn't supposed to solve all of the 8 sec, just the liquibase part, anyways I think it's a bad approach to start rolling threads for loading beans. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #294 (?)
Signed-off-by: Bonczidai Levente [email protected]