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.
close #1104
adds a metric to understand how expensive routing each message is.
currently only deals with received messages. Should we fold in transmitted messages also?
same metric? other metric?
Typically the complexity is not on transmission, but rather reception (filtering is there.)
sample output (during a static flow test) look at the... nth column... um... titled msg/scpu
I set the runStateThrehold_cpuSlow to 1000 ... which is kind of high for this, so a lot of flows show up as cpuS in the second column.