Removing DwarfFDECache at all when _LIBUNWIND_NO_HEAP=1. #1
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
Adding to that cache was already disabled in function add, but it was still checked (also with mutex).
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.
Before that
DwarfFDECache:addwas doing nothing when_LIBUNWIND_NO_HEAP=1.But the cache (which can't be filled when
adddo nothing) was still checked (also with rwmutex).That PR removes DwarfFDECache more decisively.
That should fix ClickHouse/ClickHouse#7383 and improve performance a bit (no mutex operations now when unwinding).