JS: Improve performance in API-graphs. #5200
Merged
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.
Inspired by a performance regression in
openlayers/ol2
.Evaluation looks great. (I only evaluated on
TaintedPath.ql
)./cc @tausbn, @max-schaefer (I added you guys to my evaluation-repo above).
TODO: I also did an evaluation on each commit on it's own. And I might revert theAPI::InvokeNode::getParameter
change.I can't see from an evaluation if the
API::InvokeNode::getParameter
change helps.But it saved 7.5s for
TaintedPath.ql
onol2
on my machine, so I'm keeping it.