messager: avoid taking locks if there's no work to do #4745
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.
In reviewing #4739 I noticed that the txpool calls into the messager engine on every committed transaction with the list of new messages / changed messages.
For all cases in which the transaction did not actually change a messages table, the two lists are empty, but the messager engine still takes internal locks to process these empty lists.
It seems like this could cause unnecessary lock contention, so add an initial short-circuit check in case both lists are empty.