conditional instrumentation and profiling options for server example #854
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.
I'm just going to park this here to discuss whether we want to include this in the agent.
This adds some compile-time flags for the server example app so you can easily build it with and without the agent, and with and without profiling. The default is the same as always (no profiling, yes agent). This may be of use for doing speed comparisons.
On the other hand, it does add some clutter to the code in the example app. The question is whether the benefit is worth the clutter.