Do not run expensive query in save_task if SAVE_LIMIT is 0 #639
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
On MS SQL Server, the select_for_update() query below will take a ROWLOCK,UPDLOCK on every row in the Task table. This happens because it locks every row it needs to look at to return the result of the query. Since there is no index on the default sorting column "stopped", it has to do a full table scan, and hence it will take rowlocks on each row in the table. On other databases, it will still do a full table scan, but without the excessive locking. If SAVE_LIMIT is 0 the result of this query is unused, so by moving the check a level higher we avoid running this expensive query.
rubendv
force-pushed
the
save_limit_0
branch
from
26786fb
to
32e7a35
Compare
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.
Check if SAVE_LIMIT is bigger than 0 before running any queries.
On MS SQL Server, the select_for_update() query below will take a ROWLOCK,UPDLOCK on every row in the Task table. This happens because it locks every row it needs to look at to return the result of the query. Since there is no index on the default sorting column "stopped", it has to do a full table scan, and hence it will take rowlocks on each row in the table.
On other databases, it will still do a full table scan, but without the excessive locking.
If SAVE_LIMIT is 0 the result of this query is unused, so by moving the check a level higher we avoid running this expensive query.
It might also be a good idea to optimize the query if SAVE_LIMIT is not 0, for example by putting an index on the stopped column, or by ordering this query by pk instead of the stopped column.