[Nonlinear] fix performance of evaluating univariate operators #2620
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.
With the energy modeling benchmarking that @joaquimg has been doing, we've been talking about how small things never show up in a flame graph until you look at their aggregate across multiple call sites.
One thing that shows up is
getindex
With the only giveaway being the
ht_keyindex(::Dict{Symbol,Int}, ::Symbol)
method.It's because we're calling
operators.univariate_operators[node.index]
in multiple places, which is aDict
lookup.These calls don't show much because of inlining etc. Even in the code view, you're kinda like "call is expensive. Sure"
Before
After
Script