Make comments.user_id not nullable and tweak some joins #4048
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.
This splits off joins changes from #4017
Setting the
user_id
field for comments to be not nullable makes possible to use faster inner joins. Also, I've disable thelazy='joined'
relationship property in the Update model against builds and comments: this will avoid to unconditionally load all the builds and all the comments associated to the update when we retrieve it from the database.In my opinion, this should give better performance. Locally I can see some speed improvements when loading some pages, like builds or users lists, but unfortunately the updates page list is not getting substantial improvement.
Signed-off-by: Mattia Verga mattia.verga@tiscali.it