Do not release and re-acquire dbmutex on memtable-switch if no listener #9758
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.
There is no need to release-and-acquire immediately when no listener is registered. This is
what we have been doing for
NotifyOnFlushBegin()
,NotifyOnFlushCompleted()
,NotifyOnCompactionBegin()
,NotifyOnCompactionCompleted()
, and some otherNotifyOnXX
methods in event_helpers.cc.Do the same for
NotifyOnMemTableSealed ()
.Test plan:
make check