Raise perf tracking events when formatters are dynamically generated #1829
Conversation
This file contains hidden or 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
Collaborator
Author
|
@davkean Can you look at the screenshot and tell me whether this is sufficient? I'm emitting the type name in the Start event, and the duration is reported by PerfView as part of the Stop event. This strikes me as more tedious to review than if the duration and type name were on the same event. Should I move the type name report to the Stop event, or is there a better fix? |
0be0b96 to
2f01a74
Compare
Collaborator
Author
|
I spoke with Ashok and made a change to move the type names to the Stop event so that the Start events can be largely ignored. |
This was referenced Jul 21, 2025
This was referenced Sep 19, 2025
This was referenced Oct 26, 2025
This was referenced Dec 2, 2025
This was referenced Dec 9, 2025
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.
In anticipation for MessagePack v3, where AOT formatter generation is on by default, we'd like apps using v2 and possibly migrating to v3 to be able to track perf impact of the change by observing the number of dynamically generated formatters that are generated by their application now and in the future.
Raising these events has almost no perf impact unless there is a process that is actually listening for them, and even then, they are designed by the OS to be extremely lightweight.
Here is a sample of the result, when the events are activated and traced by PerfView: