Refactor performance counters: "on-the-fly" and "on-the-fly-lw" modes #65
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
Rename the previous "on-the-fly" mode into "on-the-fly-lw": in this mode, a monitor thread will tell application threads "it's time to dump the performance counters". It is the application threads' job to dump the performance counters. It is called "lightweight" because no performance counters will be dumped if they are not changed. In the new "on-the-fly" mode, a monitor thread will directly dump the performance counters at fixed intervals. It is useful for debugging deadlocks.
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.
Rename the previous "on-the-fly" mode into "on-the-fly-lw": in this mode, a monitor thread will tell application threads "it's time to dump the performance counters". It is the application threads' job to dump the performance counters. It is called "lightweight" because no performance counters will be dumped if they are not changed.
In the new "on-the-fly" mode, a monitor thread will directly dump the performance counters at fixed intervals. It is useful for debugging deadlocks.